Output procedure

The TO-FILE operand of the CONVERT statement defines the name of the output procedure or, if two or more input procedures stored in library elements are to be converted, the names of the output procedures.

In this context, it is vital to remember that the FROM-FILE and TO-FILE values must always be different. Regardless of the format of the input procedure, a cataloged SAM file or PLAM library element is always created for the output procedure. The operand REPLACE-OLD-FILE = *YES can be used to specify that an existing file or a library element with the same name can be overwritten. No empty files or library elements are generated. This means that in the event of aborting the conversion before writing any command record to the output procedure file specified with TO-FILE, no output procedure is generated.

The output procedure contains the converted commands or the ISP command records taken over unchanged from the input procedure.
If SDF command records form part of the input procedure, the specified commands are expanded to their full command names.
Depending on the values of the DOCUMENTATION and UNCHANGED-CMD operands, the output procedure may also contain additionally added comment lines (see the table 7). These additionally inserted comment lines may be useful to the user in the following cases:

1. For manually post-editing the converted procedure (output procedure):certain ISP commands (e.g. JOIN) cannot be converted automatically as they have various SDF equivalents, the appropriate one being determined by the context. In the comment line, SDF-CONV makes a suggestion as to the appropriate conversion. This comment line is written in front of the command line with the unconverted command. The output procedure then contains the following lines:

   /"*****" REMARK <sdf-cmd = conversion proposal>

   /<isp-cmd>

2. For retaining inline comments in an ISP command record:
   If SDF-CONV encounters a command record with inline comments, the command, the operands and the operand values are converted but the comment is not transferred.Insertion of the ISP command record ensures that the information contained in the comment is not lost and can be incorporated in the command record manually if required. The output procedure contains the following lines:

   /"*****" REMARK <isp-cmd "with inline comment">

   /sdf-cmd

The following table shows the scope of the output procedure depending on the values set for the UNCHANGED-CMD and DOCUMENTATION operands. This is illustrated by way of an example based on two ISP commands:

/SYSFILE SYSLST=() /ERASE OTTO "DELETE"

-> ->

/ASSIGN-SYSLST TO-FILE=*PRIMARY /DELETE-FILE FILE-NAME=OTTO

DOC	UNCHANGED-CMD = *NO1	UNCHANGED-CMDS = isp-cmd2
*NO	/sdf-cmd ... The command is converted. /ASSIGN-SYSLST TO-FILE=*PRIMARY /DELETE-FILE FILE-NAME=OTTO	/isp-cmd ... The command is not converted. /SYSFILE SYSLST=() /ERASE OTTO "DELETE"
*MIN	/REMARK isp-cmd ...(not always) /sdf-cmd ... The command is converted. If the command is longer than one line or contains an inline comment, SDF-CONV additionally writes this record to an inserted comment line. /ASSIGN-SYSLST TO-FILE=*PRIMARY /REMARK ERASE OTTO "DELETE" /DELETE-FILE FILE-NAME=OTTO	/REMARK sdf-cmd ...   /isp-cmd ... The command is not converted, but SDF- CONV writes a conversion proposal in an inserted comment line.       /REMARK ASSIGN-SYSLST TO-FILE=*PRIMARY /SYSFILE SYSLST=() /REMARK DELETE-FILE FILE-NAME=OTTO /ERASE OTTO "DELETE"
*MAX	/REMARK isp-cmd ... /sdf-cmd ... The command is converted. In addition, SDF-CONV writes the command record to an inserted comment line. /REMARK SYSFILE SYSLST=() /ASSIGN-SYSLST TO-FILE=*PRIMARY /REMARK ERASE OTTO "DELETE" /DELETE-FILE FILE-NAME=OTTO	/REMARK sdf-cmd ... /isp-cmd ... The command is not converted, but SDF-CONV writes a conversion proposal to an inserted comment line. /REMARK ASSIGN-SYSLST TO-FILE=*PRIMARY /SYSFILE SYSLST=() /REMARK DELETE-FILE FILE-NAME=OTTO /ERASE OTTO "DELETE"

Table 7: Documentation level in the output procedure depending on the values set for the
                UNCHANGED-CMD and DOCUMENTATION operands

¹Provided conversion of the ISP command isp-cmd is not subject to any restrictions.

²Or: the ISP command cannot be converted because its meaning is context-dependent or runtime-dependent.