Packages in Limbo
To see a list of applications for limbo testing, press enter on The Monitor Packages in Limbo panel (CMNQRYL1), you’ll be presented with a list of applications:
CMNQRYL3 -------------- APPLICATION SELECTION LIST -------- Row 1 to 2 of 2
COMMAND ===> _____________________________________________ SCROLL ===> CSR
APPL DESCRIPTION HIGHEST #
S ACTP ACCOUNTS PAYABLE 000009
_ GENL GENERAL LEDGER 000003
*************************** Bottom of data *******************************
Place an S next to the APPL to be limbo queried and press enter (if you only have one application, the selection list is bypassed):
CMNQRYL2 Limbo Package List Row 1 to 1 of 1
Command ===> ________________________________________________ Scroll ===> CSR
Package Status Install Creation Level Type Request
Description
___ ACTP000001 DEV 20170528 20170205 SIMPLE PLANNED PERM
Install date has passed for this package.
**************************** Bottom of data *******************************
...
Acting on Limbo Packages
The Description row on the Limbo Package List panel (CMNQRYL2) displays the reason for flagging a package as limbo.
-
To act on a package in limbo, place the cursor in a desired row and do any of the following:
- Type DE and press Enter to physically delete the package. The package is marked for deletion, which occurs as soon as you leave this panel.
-
Type MD and press Enter to memo delete the package. ChangeMan ZMF marks the package for a memo delete.
Validate that participating packages are not associated with any super or complex package and that super or complex packages have no associated participating packages.
-
Type CD and press Enter to change the installation date of the package. Type the new change package installation date in the INSTALL field.
- Type CS and press Enter to change the package status. Type the new status in the STATUS field.
- Type S and press Enter to manually submit a job to install the package. The Submit Job From panel is displayed. Manually Submitting a Package in Limbo for Installation describes this panel.
-
Press END. This processes the commands. You can type CANCEL at the command line to exit without processing.
Manually Submitting a Package in Limbo for Installation
-
The Monitor Packages In Limbo function reads the entire ChangeMan master file and searches for any out-of-the-ordinary situations within the packages. Such situations can include any of the following:
-
Distribution without distribution acknowledgement
-
Installation date has passed
-
Package is in APR status in an ALL environment
-
Package is in INS status in an ALL, DP or D environment (baseline ripple failed or has not yet completed)
-
A temporary package's status has not been updated to TCC even though the temporary change duration has passed.
From the Limbo Package List panel, mark a package for installation by typing an S in the first column of the row (the line command field).
CMNQRYL2 Limbo Package List Row 1 to 8 of 8 Command ===> ____________________________________________ Scroll ===> CSR Package Status Install Creation Level Type Request Description ___ ACTP003803 OPN 20170307 COMPLEX PLANNED PERM Super/Complex package has an OPEN status. ... ___ ACTP003824 DEV 20170416 20170406 SIMPLE UNPLANNED PERM Install date has passed for this package. ___ ACTP003825 DEV 20170411 20170411 SIMPLE PLANNED PERM Install date has passed for this package. S ACTP003826 DIS 20170411 20170411 SIMPLE PLANNED PERM Install date has passed for this package. **************************** Bottom of data ******************************...
-
-
Press Enter. A panel similar to the following panel is displayed.
CMNRMTSL ------------- ACTP - SITE SELECTION LIST -------- Row 1 to 1 of 1 COMMAND ===> ____________________________________________ SCROLL ===> CSR SITE NAME S C001 ***************************** Bottom of data ******************************...
-
Press END. ChangeMan ZMF presents you with a list of jobs from the X.node dataset for selection. This panel displays the contents of the '.X' staging library. Each member is a job in the package installation process. Any member that did not run to completion can be resubmitted by entering 'S' in the line command field. Use caution when submitting a job that has partially completed. All steps will run again. For example, if this is a baseline ripple job, some library types may have rippled, and resubmission will cause those libraries to be rippled again. We recommend that you first edit the X dataset and delete the jobsteps that have run successfully, or perform Installation Jobs a step restart. Then resubmit the job from the '.X' dataset or, if submission by ChangeMan is required, use this panel:
CMNQRYL4 Submit Job From X.node Row 1 to 18 of 18 Command ===> ____________________________________________ Scroll ===> CSR Source dataset name: CMNTP.ACTP.STG@.\#003826.X.C001 Name Status vv.mm Created Changed Size Init User _ ACTP1026 01.01 2017/04/11 2017/04/11 09:22 59 59 USER014 _ ACTP1126 01.01 2017/04/11 2017/04/11 09:22 63 63 USER014 _ ACTP1526 01.01 2017/04/11 2017/04/11 09:22 50 50 USER014 ... _ ACTP6426 01.01 2017/04/11 2017/04/11 09:22 67 67 USER014 S ACTP6526 01.01 2017/04/11 2017/04/11 09:22 51 51 USER014 **************************** Bottom of data *******************************...
-
Place an S next to the job for submission and press enter:
CMNQRYL4 Submit Job From X.node Row 1 to 18 of 18 Command ===> ____________________________________________ Scroll ===> CSR Source dataset name: CMNTP.ACTP.STG@.#003826.X.C001 Name Status vv.mm Created Changed Size Init User _ ACTP1026 01.01 2017/04/11 2017/04/11 09:22 59 59 USER014 _ ACTP1126 01.01 2017/04/11 2017/04/11 09:22 63 63 USER014 _ ACTP1526 01.01 2017/04/11 2017/04/11 09:22 50 50 USER014 ... _ ACTP6426 01.01 2017/04/11 2017/04/11 09:22 67 67 USER014 _ ACTP6526 *Select 01.01 2017/04/11 2017/04/11 09:22 51 51 USER014...
-
Your job is submitted.