How do I verify whether my dialog is at the correct level or not?

Ensure you have migrated the CustomPac Installation Dialog to level 27.20.00 or higher. You can determine the level of the CustomPac Installation Dialog you are using by checking the upper right hand corner of the primary panel CPPPPOLI. For additional information on the migration action refer to the “Chapter 3. Installing and Starting the Dialog” in CustomPac Installation Dialog Reference Manual book or z/OS Migration manuals.

I am currently performing my install using SystemPac, I received CPP0612015 ERROR BROWSING STORED OUTPUT IN SCPPOENU when I tried to use O-Output to look for the job output after the job ran. Why can’t I view my output?

To use the 'O' command:

  1. The jobname must be your userid + character unless you have a TSO Output exit which allows other jobnames.
  2. The variable OUTPUT LOGGING must be set to ‘YES’.
  3. The MSGCLASS in your job must be a held output class.

I can't see my order any more.  Is it gone?

No, your order has probably just been place in “Finalized” status. Follow these steps to change the status:

  1. Once in the dialogs enter D  DISPLAY - Select Orders to Display
  2. On the subsequent panel enter Y for all values.
  3. Once the list of orders is displayed, select your order with the E (Edit) command
  4. Change the Status to S for Started, hit enter.

Why do I receive the following error?

This error is usually caused by your ISPPROF data set running out of extents or directory blocks.

Delete and reallocate your ISPPROF data set larger and with more directory blocks and retry the operation.

I am installing CICS using the SystemPac. I have made the changes to the variables (ds name prefixes, etc) and saved them. When I review the installation jobs, none of my variables are reflected in the data set naming. Why not?

The data set name variables are used in the CICS clists to configure CICS. The actual names of the data sets are specified in the Modify System Layout panel. You will need to modify the names in the Modify System Layout to reflect the actual data set names you want.

There are various global commands you can use once in the data set name displays. Typing HELP will show the possible CHD commands. If the result of a change is not what you wanted, just enter B on the primary Modify System Layout panel and it will not save the changes made in this session.

Where do I find an explanation of the variable(s) represented in the 'Synonym' columns so that I may assign proper values to them?

Placing a B beside the variable and pressing enter twice will present a short description of the variable and what it is used for. Description of the variable(s) is also documented in the Installing Your Order document in the section titled 'Appendix B. Variables Used in This Order'.

I encountered an error “/*003*/ LISTDSI SCPPEENU” after porting my dialogs to the target system, what is wrong?

When porting the dialogs from the driving system to the target system, both the Master set of dialogs and the Order set of the dialogs must be moved to the target system to use the ServerPac dialogs. The noted error message indicates that the System is unable to locate the Order set of the dialogs.


On the panel CPPP610A, I specified a volume which is physically online on the driving system. Why do I still get the CPP0610020E message?

When receiving an order, the dialog will try to dynamically allocate a data set using the Data Set Qualifier specified in panel CPPP610A. If your security product does not allow such allocation, dialog will return the CPP0610020E message even though the volume is online.


On step "UC ;- Update Configuration with Target Environment Data", I get the error CPP9999996S Unexpected DIALOG ERROR:
Contents of the ISPEXEC buffer was:

The UC Option is trying to locate the catalog entries of the existing data sets.  Verify that the catalog entries for all the SMPE CSI and data sets are correct, and confirm that the data sets are not corrupted.  If still not able to locate the error, you may turn on the DEBUG mode by enter DEBUG in the COMMAND field.