Constructing Command Lines to Create and Apply Change Packages
Apply commands include:
-
CPDEFINE = Define a New Change Package
-
CPAPPLY = Apply Previously Created (non-PRP) Change Package
-
PRPAPPLY = Apply PRP
-
PTPAPPLY = Apply a patch to your Current PeopleTools Release
-
PTUAPPLY = Upgrade to a New Release of PeopleTools
-
UPGAPPLY = Application Upgrade
-
DLTAPPLY = Apply Tools Delta Package
-
TDPAPPLY = Apply Translation Delta Package
-
RFUAPPLY = Apply Required for Upgrade Package
When you run the command line, the error codes are as follows:
-
0 = Success
-
1 = Failure
-
2 = Manual Stop encountered
-
3 = Failed to get lock
-
4 = Job completed with warnings
The RESUMEJOB parameter has the following limitations:
-
COMPLETECONTINUE cannot be used for a failed Filter Query step
If the pending job is stopped by a failed Filter Query step, -RESUMEJOB can only have the value of RESTARTCONTINUE or READYTORUNCONTINUE. If the value is COMPLETECONTINUE , an error message is reported.
-
RESTARTCONTINUE| READYTORUNCONTINUE cannot be used for a manual stop step.
If the pending job is stopped by a manual stop step, -RESUMEJOB can only have the value of COMPLETECONTINUE. If the value is RESTARTCONTINUE or READYTORUNCONTINUE, an error message is reported.
-
The job must exist in Change Assistant Database in order to use RESUMEJOB.
If there is no job set in progress when the CA apply command line is run with the parameter - RESUMEJOB, a warning message is reported.
-
RESUMEJOB cannot be used when the parameter RESETJOB is Y.
If there is a job in progress and the -RESETJOB parameters is set as Y or not set (the default value is Y) a warning message is reported as The resuming job can’t be reset.
-
All other parameters need to be consist with the parameters of existing job
If there is a job in progress but the job parameters are not consistent with the ones in CA apply command line; a warning message is reported as The pending job can’t be resumed by the inconsistent parameter values.
Note:
From 8.60, you can create and apply change packages from separate jobs. Earlier defining, creating, and applying change package was executed consecutively in change assistant command line mode in a single job.