Special Usage Considerations › Pre-Validation Variable Substitution › The CHANGE Option and the CHANGE Conversion Table

The CHANGE Option and the CHANGE Conversion Table

To use this feature do the following:

1. Specify the CHANGE runtime option:
   • In batch, specify this option in the CA JCLCheck options file.
   • In EDCHEK, specify this option in the EDCHKDD DD file or on the EDCHEK command string, for example:
     %EJCK CHANGE(target,dsname[,member])
   • In ISPF, specify this option in the CA JCLCheck options file or on the ADDITIONAL PROCESSING OPTIONS menu (panel JCK0203).

   Note: For information on the CHANGE runtime option, see the Command Reference Guide.

2. Create a PDS member or sequential file containing the user-defined conversion table. The file containing the conversion table is specified in the CHANGE option. This table contains the 'from' and 'to' data strings. In ISPF, the CHANGE option and all of its sub-options can be specified on the ADDITIONAL PROCESSING OPTIONS menu (panel JCK0203).

There are four types of statements in the CHANGE conversion table:

LEFT DLM a

This statement defines the left delimiter that is used on the 'from' and 'to' data strings for all following CHANGE statements. If omitted, CA JCLCheck uses the default open-parenthesis `(' as the left delimiter on both the 'from' and 'to' data strings.

RIGHT DLM z

This statement defines the right delimiter that is used on the 'from' and 'to' data strings for all following CHANGE statements. If omitted, CA JCLCheck uses the default close-parenthesis `)' as the right delimiter on both the 'from' and 'to' data strings.

An asterisk (*) in column 1

This statement is ignored by CA JCLCheck and can be used as a comment.

CHANGE afffz=atttz

This is the format of a standard CHANGE statement. It must begin in column 1 and must contain the following 7 characters: 'CHANGE ', immediately followed by the 'from' data string consisting of one or more characters that CA JCLCheck will search for, surrounded by a left and right delimiter. The 'from' data string must be immediately followed by an equal sign (=), which must be immediately followed by the 'to' data string that CA JCLCheck will use as a replacement value, also surrounded by a left and right delimiter.

If a CHANGE statement is in the format CHANGE afffz=az (with an empty 'to' data string), the CHANGE statement causes the 'from' data string to be deleted without replacing the string with a 'to' data string.

Example: CHANGE conversion table with explicit delimiters

The following example shows a CHANGE conversion table with an explicit left delimiter and right delimiter specification:

LEFT DLM [
RIGHT DLM ]
CHANGE [>?<]=[SHD]      
CHANGE [><]=[ID]        
CHANGE [::!!¢!]=[YYMMME]
CHANGE [!!¢!::]=[MMMEYY]

Example: CHANGE conversion table with implied delimiters

The following example shows a CHANGE conversion table with an implied left delimiter and right delimiter using the default left and right parenthesis as delimiters:

CHANGE (¢%)=(MM)   
CHANGE (!%)=(YY)   
CHANGE (%$)=(CC)   
CHANGE (¢$)=(SC)   
CHANGE (_@_)=(X)   
CHANGE (_?_)=(1)   
CHANGE (@)=(X)     
CHANGE (?)=(1) 
CHANGE (@*#)=()   
CHANGE (%S.)=(##.) 
CHANGE (=%S)=(=##) 
CHANGE ('%S')=('##')

The following are restrictions regarding the CHANGE statements:

• All statements in the conversion table must start in column 1 and must not include imbedded blanks unless they are enclosed within the left and right delimiters.
• A CHANGE statement cannot continue onto a second line.
• The maximum length of each 'from' and 'to' data string is limited to 30 characters.