Find Answers

Filter Search Results

Ask a Question

Example: "Database could not be verified"

Tips | Start Over | Solutions | Alerts | Patches | Defects

Pages [Next]

Results

CMN55 not triggered for REMOTE site when performing a BACKOUT.

CMN55 not triggered for REMOTE site when performing a BACKOUT.

CMN55 Job does not check Package Status on the DP site

CMN55 Job does not check Package Status on the DP site

CMN55 job is submitted twice

CMN55 job is submitted twice

Similar Answers

CMN55 job hanging in DSPTM step during reverse ripple

CMN55 job hanging in DSPTM step during reverse ripple

Similar Answers

Remove CMN$$PCP from skels CMN20 + CMN55

Remove CMN $$PCP from skels CMN 20 + CMN55

CMN55 job does not get submitted by the CMN54 job

CMN55 job does not get submitted by the CMN 54 job

Components not being 'rippled' by CMN30 and CMN55

Components not being 'rippled' by CMN 30 and CMN55

Error in Backout Skeleton CMN55PDS for CMN55CPI imbed. (Only occurs if IMS is licensed.)

Error in Backout Skeleton CMN55 PDS for CMN55 CPI imbed. (Only occurs if IMS is licensed.)

CMN37 DELAY processing is broken and RC checking is incorrect for INS and BAK.

When the CMNDSPTM step fails during CMN 30 or CMN55 JOB execution, the CMN 37 JOB gets logged to the CMNDELAY file, but the package status is not changed. When the task is cycled, the CMN37 JOB executes, but since the package status is not BAS, the first step fails and the job is flushed and not added back to the delay file.

CMN4524I issued during backout after change to BUN table

If the original package is subsequently backed out the DSPTM step in the CMN55 reverse ripple job will end with a RC=4, the following type of messages and IMPACT/LDSLOAD will need to be rerun:

Pages [Next]

Welcome kb sso

My Recent Searches

	cmn55
	dimensions cm crash dump
	stop responding
	.Update()
	da agent Connected
	install araxis merge