Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Basic preconditions and restrictions

&pagelevel(4)&pagelevel

  • Error-free procedures in ISP format are a basic prerequisite for producing error-free procedures in SDF format.

  • SDF-CONV only converts ISP commands that were defined in BS2000 versions ≤ V10.

  • The FROM-FILE and TO-FILE operands must always be assigned different values. This applies even if the operand REPLACE-OLD-FILE = *YES is specified.

  • Every command in the input procedure that is not described in one of the syntax files is copied unchanged to the output procedure. An error message is output to SYSLST.

  • All commands which refer to card readers are copied unchanged to the output procedure, because such devices ceased to be supported by BS2000 with the release of V10.0.

  • Operands to which no explicit values have been assigned can be generated for SDF commands. These operands implicitly receive the default value specified in the operand description of the relevant command (see the the “Commands“ manual [1]).

  • Procedure parameters must not be part of a command or operand and must not themselves be either a command or an operand.

    Example

    /PROC N,(&PARAM1 = 'SHOW', &PARAM2 = 'FILE')
    /...
    /&PARAM1-SDF-OPTIONS
    /CREATE-FILE &PARAM2 = OTTO.DAT
    /...
    /ENDP 
    
  • Commands containing procedure parameters can be converted to SDF format only if their conversion is not dependent on the parameters. In all other cases no one-to-one assignment can be made, and so the commands are not converted (cf. "Non-convertible operand configurations and conditional conversions "ff).

    Example

    /PROC N,(&USE1)
    /...
    /RFD USE=&USE1
    /...
    /ENDP 
    &USE1 = NO      is converted in SDF to:  /STOP-DISKETTE-INPUT
    &USE1 = INPUT   is converted in SDF to:  /START-DISKETTE-INPUT 
    
  • If the input procedure contains the SDF command MODIFY-SDF-OPTIONS, the value of the CONTINUATION operand must not be a procedure parameter.

  • If the input procedure contains the SDF command ENDP-RESUME and the output procedure is to be an S procedure, the command is converted into EXIT-PROCEDURE RESUME=YES.If the ouput procedure is to be a non-S procedure, the command is not converted since the procedure's spin-off mechanism is different in this case.

  • All names beginning with an asterisk and containing no other wildcards are interpreted as keywords.

  • The old label format (.label) is not converted into the new label format (label:).

  • SDF-CONV does not recognize nested procedure parameters or nested replaceable job variables when converting ISP commands from S procedures into SDF commands, so that the command records concerned are not converted.

  • Successful conversion of the command language causes inline comments in commands from the input procedure to be lost. This can be avoided by specifying the CONVERT statement operand DOCUMENTATION=*MIN/*MAX, which causes inline comments to be transferred to the output procedure.