Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML 8.1.2 P-site not submitting CMN20 job after CMN21 when package developed on earlier version instance
8.1.2 P-site not submitting CMN20 job after CMN21 when package developed on earlier version instance
CMS-XML Installation site updates causing invalid or non-submission of CMN21 job
In CMN ZMF 5.5.1 under DEF80035 (CHGMAN tries to submit 21 job instead of 20 job ) Serena implemented a solution to the problem where CMN21 jobs were being submitted instead of CMN20 jobs in certain circumstances. Additional safeguards were added to the freeze/install JCL-build process to avoid the potential for this happening.
CMS-XML ERO: CMN21 jobs are not submitted during package install, leading to DB2 timestamp errors.
The installs of ERO packages, with DB2 components, are not submitting the CMN21 jobs. However the CMN20 jobs were submitted . This caused -805 DB2 errors in the customer's PROD environment.
CMS-XML CHGMAN tries to submit 21 job instead of 20 job
If they create a package with 22 sites, then later use U7 to add additional sites. Then during the install process ChangeMan tries to submit a CMN21 job instead of a CMN20 job for the site added from U7. Even more interesting the package NEVER contained any DB2 components. Also found out that the ISIT record in the staging .PACKAGE has x'01' in the DB2 Install Bind Job Counter field for the sites that were added through U7.
CMS-XML No log record written when install fails in CMN21 rather than CMN20
On a "DP" or "P" site, failure submits new job CMN26. CMN 26 submits job CMN 27 of the "D" or "DP" development site. CMN27 executes CMNBATCH transaction 99 with NOD=DP/P production site name and FUN=21 on the "D"/"DP" site.
CMS-XML Reinstall of DB2 package on P site via monitor.limbo does not submit CMN20. Subsequent backout does not submit CMN49.
3. logon to P site and issue the backout. 4. use monitor.limbo to submit the reinstall. CMN21 is the first job in a DB2 install on a P site.
CMS-XML ACF2 customers are receiving "ACF01009 LOGONID NOT VALID FOR SUBMISSION BY PROGRAM - CMNWAKUP"
Another customer reports that after setting up a new user ID as indicated in S143215, when there are DB2 components in the package, the CMN21 job runs first and submits the CMN20 job . The CMN20 job fails as it is now setup to use the new user ID. The customer coded logic in the skels to only use the NEW ID in the CMN20 job when there are no DB2 components in the package.
CMS-XML New Features in ChangeMan ZMF 8.2 Patch 3
However, in previous ZMF releases, if the package contains Db2 components, the CMN21 (instead of CMN20 ) job is submitted . If CMN21 fails for any reason, the CMN29 job is not submitted
CMS-XML Urgent Notices for ChangeMan ZMF
Urgent notices for ChangeMan ZMF Essential maintenance required for all customers upgrading to ZMF 8.1.2. 1) Component master corruption following conversion to 8.1.2 from releases below 7.1.3. 2) Install job ( CMN20 ) is not submitted upon completion of CMN21 .
CMS-XML ZMF 8.1.2. Essential maintenance required for all customers upgrading to ZMF 8.1.2.
2) DEF293091 - In a staggered upgrade environment where P sites are upgraded to ZMF 8.1.2 prior to D or DP sites, installs to the P site will not submit the CMN20 job following the execution of CMN21 . Obtaining the ZMF 8.1.2 compatible hotfix: Further information and the hotfix for these problems can be obtained from Solution S141939 .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs