Changes to Customization Dialog

This topic lists the changes to Customization Dialog of SA z/OS® 4.2.

  • The specification of the entry type Application Group (APG) has been changed. The Define New Entry panel requires specification of Type, Nature, and Model and does not supply any default vales. The values specified in the new processing cannot be changed later. After initial conversion of the PDB to the new 4.2 level, further changes of the group nature also for existing groups will not be possible. In order to change the nature, you have to delete existing group and create new one with the required Type/Nature/Model.
  • With SA z/OS 4.2, some specifications of entry type Application Group (APG) for NEW and UPD have changed. Down-level specifications are not accepted. Use File Update to create a file in the new format and update the NEW and UPD sections accordingly.
  • Due to the new layout of CODE definitions for message ID CAPMSGS, the flat file layout also changes. Therefore, to import a flat file created with an older SA version, the layout of CAPMSGS code processing in the flat file must be changed to the following format. Otherwise, syntax errors will be reported during the import. 
    Message ID                          : CAPMSGS     
  Description                       :
  Action                            - CODE        
    Message ID                      :  
    Jobname                         :       
    User (CODE3)                    : 
    Severity                        : 
    Alert                           :         
    Inform List                     : 
    Comment Type                    :         
    Comment Text                    :   
    DOM List                        :

    After line Action - CODE for each 'code matching' record, the bold lines are required.

    Message ID was Code 1 in the prior format of the flat file. Jobname was Code 2 in the prior format of the flat file. User (CODE3) was Code 3 in the prior format of the flat file. Severity was Value Returned in the prior format of the flat file.

  • Due to the new layout for CODE definitions for message ID CAPMSGS, the PDB must be converted to the new layout. It means that during the initial conversion (first open) of the PDB, the definitions of message ID CAPMSGS are automatically converted to the new layout. This change cannot not be reversed. A PDB already converted cannot be opened with a Customization Dialog of an older SA release.
  • Due to the new INGALERT definitions for critical WTORs, an additional record is created in the PDB if a definition with CODE1=CRITICAL_WTOR is available. The new record for message ID INGALERT shows CODE1=WTOR/*, and CODE2, CODE3, and VALUE RETURNED are copied from the existing records.

    It means that during the initial conversion (first open) of the PDB, the definitions of message ID INGALERT are automatically converted to the new layout. This change cannot not be reversed. A PDB already converted cannot be opened with a Customization Dialog of an older SA release.

  • If you want to use the generated configuration files on a system with an older SA level, compatibility APARs (at least APAR OA54684) must be installed.