Configuring Your Product › Tailoring and Other Considerations › User-Specified Condition Codes

User-Specified Condition Codes

CA Disk assigns a step completion condition code to every step. The code accompanies a message and indicates the circumstances under which the step finished. In most cases, this CA Disk-generated condition code is the best value for your installation. However, you can override these generated condition codes if your installation has special requirements. This override allows you to select the code that accompanies a message upon the completion of a step. These user-specified condition codes are optional.

Note: A similar option is available for those instances where NO CATALOG ENTRIES WERE FOUND exists when DSCL is searching for candidate data sets. For more information, see the sysparm CCDRESETn in the chapter "Sysparms."

To specify user condition codes, you must create a member in PARMLIB called CCSET. This member is not provided with the system, although a member called SAMPCSET is provided as a sample, and can be copied to create your initial CCSET. User condition codes are then specified by an entry in this member.

When using this option, several technical points must be kept in mind with respect to user condition code processing.

1. Once an N (no-override) is encountered during processing, CA Disk determines sets and assigns condition codes for all the message number entries that follow without regard for the overrides specified in member CCSET.
2. Whenever a message is issued during step processing, the highest condition code is set without regard to its origin.
3. Before CA Disk returns control to the operating system, a check of the CA Disk-generated return code is made. If the CA Disk return code is odd and the user condition code option is in effect, then the user override condition code is incremented by one. For example, if the user specified an override condition code of 4 and the CA Disk generated condition code is odd, then the user override condition code of 4 is incremented to 5. This is needed to produce sorted report listings.
4. No duplicate message number entries are allowed in member CCSET. If duplicates are detected at table initialization, the program abends with a user 200.

   Each CCSET entry is composed of a message number, a state flag (O=override or N=no-override), and one of five possible condition codes. The message number is the first four positions followed by a blank. The next two positions consist of the state flag and a condition code respectively.

   To add, change, or delete entries in the CCSET member, use your online editor or other conventional means for updating a PDS member in the following manner:

   1. Create a member named CCSET in the PARMLIB data set by copying and renaming the sample member SAMPCSET.
   2. Specify the message display control entry in CCSET. This must be the FIRST entry in CCSET and is required. This entry controls the display of the message, which notifies users that the user condition code option is in effect. It is recommended that you try the default first which displays the message in BATCH and TSO. The format for $FLGXyz is as follows:

In order to suppress the display of the notify message under BATCH or TSO processing, simply blank out the respective flag. If you want to suppress the display of the notify message under BATCH and TSO processing, blank out both flags.

1. Specify the message number, state flag and condition code enclosed by apostrophes in the CCSET member. An example can be:

   '3179 OE'
   

   The format for message number, state code, and condition code is shown in the following table:

The valid entries for MMMMBsc are shown in the following table: