Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

CALL-BCAM-COMMANDS: Process commands from a file

&pagelevel(3)&pagelevel

You use this command to initialize the processing of BCAM commands from a file.
This command can also be used to start an SOF file with BCAM running. The DCOPT command of the SOF file is ignored in this case.

To control processing of the BCAM command file as a function of the results, you can use the BCOPTION CMDFILE-CONTINUATION and the following branching instructions (see also section "Command sequences"):

  • /IF-BCAM-ACK

  • /IF-BCAM-NAK

  • /ELSE-BCAM

  • /END-IF-BCAM

In addition, the host- and system-specific branching instructions can also be used to control command sequences. A detailed description of how these are controlled is provided in the section "Command sequences".

To improve the overview it is possible to display remark lines in the command file. The remark lines begin with * in the first column or with /REMARK.

If an SOF or command file is being edited, no other command file can be started via the console until it has been processed. However, it is possible to call up to seven further command files from an SOF or a command file.

The alias name CLBCCMD exists for CALL-BCAM-COMMANDS.

BS2000 console

BS2000 SDF command

Command/SOF file

SNMP management

Parameter service

x


x



List of valid command sources

CALL-BCAM-COMMANDS / CLBCCMD

FILE-NAME = <filename 1 .. 54>

,TIME-LIMIT = 600 / <integer 1 .. 99999999>

,SYNTAX-CHECK-ONLY = *OFF / *ON / *ERROR-ONLY

FILE-NAME=<filename 1..54>
Specifies the name of the file containing the BCAM commands. If the command file does not exist under the TSOS system administrator ID, the file name must be fully qualified including USERID. In any case the filename of the command file must be cataloged in the home pubset, otherwise errors can occur in connection with files cataloged on data pubsets or shared pubsets.

TIME-LIMIT=<integer 1..99999999>
Specifies the monitoring period (specification in seconds) for the processing of the command file.
1 < 600 < 99999999 sec

SYNTAX-CHECK-ONLY=...
Controls the processing of the command file. As an alternative to the normal processing of the command file, you can also use the SYNTAX-CHECK-ONLY operand to initiate a syntax check of the BCAM commands present in the command file. In this case the commands are not executed.

SYNTAX-CHECK-ONLY=*OFF
All the commands present in the command file – with the exception of DCSTART and DCSOF – are processed normally.

SYNTAX-CHECK-ONLY=*ON
All the BCAM commands are subjected to a syntax check and all the other commands are ignored. No commands are executed.
Logging is performed using the messages BCA0769 (syntactically correct) and BCA0768 (syntax error).

SYNTAX-CHECK-ONLY=*ERROR-ONLY
All the BCAM commands are subjected to a syntax check and all the other commands are ignored. No commands are executed.
However, in contrast to the *ON parameter, only syntactically wrong commands are logged.

Command logging

The processing acknowledgment is supplied in news BCA0890 if it is positive and in news BCA089E if it is negative. In addition, for positive acknowledgments, the messages BCA0769 and BCA076C may appear.
A description of the error messages that can be issued during command processing is provided in the table below.

Command return codes

(SC2)      SC1

Maincode

Meaning

   0        0

CMD0001

Command successfully processed

   0        1

CMD0202

Error in command

   2        0

BCA089E

Command file editing cancelled

   0        1

BCA0768

Syntax error in command

   0        1

BCA089D

Command too long

   0       64

BCA0777

Interface used for...

   0       64

BCA0898

TIMEOUT of editing command file

   0      128

BCA0814

BCAM is being terminated abnormally

   0      128

BCA0816

BCAM is terminating

   0      128

BCA08B0

Another command file or SOF being edited

   0      130

BCA0766

BCAM is not active