The first command of a SOF must always be the DCOPT command. The only exceptions are the two host- and system-specific branching instructions which may also precede the DCOPT command (see the section "Command sequences", IF-BCAM-HOST and IF-BCAM-SYSINF). The settings for the DCSTART command are therefore already defined in the SOF. In the DCSTART command, you need then only specify the name of the SOF using the DCSOF operand. Any additional specifications modify the values predefined with DCOPT for this startup. This means that operands in the DCSTART command overwrite the corresponding operands in the DCOPT set, if the BCAM data communication system is started with an SOF.
A slash (/) must be specified before the operation code of all commandsin an SOF.
The DCOPT command can be written with continuation lines in the SOF. ’-’ must be used as the continuation character. This continuation character can be at any column position in the line, provided it is the last character. The continuation line must begin with a slash (/).
The DCOPT command is skipped and ignored in the command file.
BS2000 console | BS2000 SDF command | Command/ SOF file | SNMP management | Parameter service |
x |
List of valid command sources
DCOPT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HOST=...
Name of the BS2000 system, as it was specified in the RDF.
HOST= *none
No specification of the host name, the host name must be given either in the DCOPT or the DCSTART command.
HOST=<host-name 1..8>
Specification of the host name.
DCRDF=...
Refers to the name of the file which contains the network description (RDF). The RDF must always be cataloged in the home pubset, otherwise errors can occur in connection with files cataloged on data pubsets or shared pubsets.
DCRDF= *none
No RDF is explicitly specified.
BCAM default is $TSOS.DCRDF in this case.
DCRDF=<filename 1..54>
Name of the RDF
The fully qualified file name is to be specified if the RDF does not exist under the TSOS user ID.
DCRDF=*NONE,...
When *NONE is specified, startup occurs without an RDF.
MAXTSDU=...
This operand describes the maximum receive message length for the host.
MAXTSDU=*none
No specification of the maximum message length.
MAXTSDU=<integer 4096..65530>
Specification of the maximum message length in bytes.
Default: 4096
LWRESD=...
With the LWRESD operand you specify whether LWRESD can be started automatically.
In a BS2000 parameter file (parameter service) LWRESD=NO must be specified.
LWRESD=YES
LWRESD is started automatically.
Default: YES
LWRESD=NO
LWRESD is not started automatically. NO must be selected in the case of a BCAM early start (parameter service).
JV-READY=...
Name of the job variable in which the BCAM state is displayed. If the content of the job variable is "BCAM READY", the active state of BCAM is displayed. Any other content indicates that BCAM is not ready.
The BCAM job variable is reset only if BCAM is terminated normally (message BCA0716); in all other cases, it must be reset manually by the system administrator. If no job variable is available, BCAM does not log the BCAM state.
The JV-READY parameter cannot be used in a BS2000 parameter file (parameter service). The JV subsystem must be active by the time "BCAM READY" is displayed.
JV-READY= *none
The specification of the use of a job variable for monitoring the BCAM operating mode is omitted.
JV-READY=<filename 1..54>
Defines the name of the job variable which displays the BCAM operating mode. The JV must always be cataloged in the home pubset, otherwise errors may occur in connection with JVs cataloged on data pubsets or shared pubsets.
JV-RDFNAME=...
Name of the job variable in which the name of the current RDF is stored – equivalent to entry in operand DCRDF. If the content of the job variable is “NONE”, this indicates that BCAM is operated without RDF (RDF-less operation).
The BCAM job variable is only reset if BCAM is terminated normally (message BCA0716), in all other cases it must be manually reset by the system administrator. If no job variable is available, the current RDF name is not logged by BCAM.
The JV-RDFNAME parameter cannot be used in a BS2000 parameter file (parameter service). The JV subsystem must be active by the time “BCAM READY” is displayed.
JV-RDFNAME= *none
The specification of the use of a job variable for monitoring the RDF name is omitted.
JV-RDFNAME=<filename 1..54>
Defines the file name of the job variable in which the current RDF name is stored. The job variable must always be cataloged in the home pubset, otherwise errors may occur in connection with JVs cataloged on data pubsets or shared pubsets.
JV-BCAM-STATUS=...
Name of the job variable in which the current BCAM status is displayed (see "Event monitoring using BCAM job variables"). The BCAM job variable is reset only if BCAM is terminated normally (message BCA0716). In all other cases, it must be reset by the system administrator manually. If no job variable is available, BCAM does not log the current BCAM state.
The JV-BCAM-STATUS parameter cannot be used in a BS2000 parameter file (parameter service).
The JV subsystem must be active by the time "BCAM READY" is displayed.
JV-BCAM-STATUS= *none
The specification of the use of a job variable for monitoring the BCAM operating mode is omitted.
JV-BCAM-STATUS=<filename 1..54>
Defines the name of the job variable in which the current BCAM-Status is stored. The job variable must always be cataloged in the home pubset, otherwise errors may occur in connection with JVs cataloged on data pubsets or shared pubsets.
MAXNPA=...
Restricts the number of applications that are not predefined which may be opened simultaneously in the BS2000 system.
MAXNPA= *none
The specification of the number of applications that are not predefined is omitted.
MAXNPA=<integer 1..2147483647>
Number of applications that are not predefined which may be opened simultaneously in the BS2000 system.
Default: 20000
MAXNPT=...
Restricts the number of applications that are not predefined which may be opened simultaneously in the BS2000 system by a single TASK.
MAXNPT= *none
No specification of the number of applications that are not predefined.
MAXNPT=<integer 1..2147483647>
Number of applications that are not predefined which may be opened simultaneously in the BS2000 system by a single TASK.
Default: 20000
MAXCNN=...
Restricts the number of connections which an application that is not predefined may simultaneously maintain.
MAXCNN= *none
The specification of the number of connections is omitted.
MAXCNN=<integer 1..2147483647>
Number of connections which an application that is not predefined may simultaneously maintain.
Default: 20000
PAGMEM=...
With this operand, the size of the pageable memory (backup storage, paging memory, paging area), which BCAM may use for data transfer, is specified in Kbytes.
PAGMEM= *none
The specification of the size of the pageable memory is omitted.
PAGMEM=<integer 1024..1048576>
Size of the pageable memory in Kbytes.
Default: system-dependent; see also the following table for RESMEM=...
RESMEM=...
Specifies the size (in Kbytes) of the resident memory (MEM-RES) that may be used by BCAM for data transfers.
memory size in MB | RESMEM in Kbytes | PAGMEM in Kbytes |
up to 50 | 5000 | 3000 |
50 to 100 | 10000 | 6000 |
100 to 200 | 20000 | 12000 |
200 to 500 | 40000 | 30000 |
500 to 1000 | 60000 | 60000 |
over 1000 | 100000 | 100000 |
RESMEM= *none
The default system-dependent value set by BCAM is unchanged.
RESMEM=<integer 1024..1048576>
The value for RESMEM is changed.
SOKHOST=...
Specifies the socket host name of the host.
SOKHOST= *none
The specification of the socket host name is omitted.
The host name is used as the socket host name; it is extended with blanks to the length of the socket host name.
SOKHOST=<text 1..32> / <c-string 1..32>
Socket host name of the host.
PRIVPORT#=...
With PRIVPORT#, the first socket port number which can be occupied by non-privileged applications is specified.
Low socket port numbers (with the exception of port number 20) may only be occupied by privileged applications. Privileged applications are those which run under the TSOS or NET-ADMINISTRATION BS2000 system privileges.
PRIVPORT#= *none
The value 2050 set as the default by BCAM is not changed.
PRIVPORT#=<integer 1..65535>
Defines the first free port number which can be occupied by non-privileged applications. PRIVPORT# must always be less than or equal to FREEPORT#. If PRIVPORT# is larger than FREEPORT#, the value is set to the specification for FREEPORT#.
FREEPORT#=...
Specifies the first free port number which BCAM may dynamically occupy for an application. If SNMP-AGENTS is used on this processor, the port number is 3161 for the internal BCAM communication between master and subagent.
FREEPORT#= *none
The value 4096 set as the default by BCAM remains unchanged.
FREEPORT#=<integer 1..65535>
Defines the first free port number.
FREEPORT# must always be greater than or equal to PRIVPORT#. If FREEPORT# is smaller than PRIVPORT#, the value is set to the specification for PRIVPORT#.
MSG=...
Controls the extent of the message output.
The BCAM messages are described in chapter "Messages".
MSG=*unchanged
The value ALL set as the default by BCAM remains unchanged.
MSG=ALL
All messages are output.
MSG=NAK
Certain positive messages for processors are not output.
The message for directly addressed systems is always output (otherwise sequences may run incorrectly). Positive messages are suppressed only for the subsequent systems.
The following positive messages are suppressed:
BCA0740
BCA0763 for the BCIN (format 1), BCACT, BCDAC, BCOUT commands
BCA082A
BCA083F
BCA0851 with reason 00/01/02
BCA0852
BCA0853
BCA0854 with reason 00/01/02
BCA0856
BCA085B with reason 00/01/02
BCA085F
BCA08D7
BCA08DB
BCA08DC
BCA08DD
BCA08DE
BCA08DF
BCA08E5
MSG=ERROR-ONLY
Only negative messages are output.
This setting makes it possible to start BCAM more quickly (Quick Startup).
All messages that have the Weight Code 50, 70 and 99 in the message file are output. This corresponds to filter level 3 or 4 and "not suppressible at the operator terminal".
You can modify this setting with /BCMOD MSG=ALL/NAK. You should change this setting after BCAM start if you want to resume the logging of all BCAM commands.
#BITMAP=...
Number of 256 byte-long bitmaps for administering each data slotpool. If this value is not specified, it is derived from the system memory MEMORY-SIZE as follows:
MEMORY-SIZE in Mbytes | Number of bitmaps |
up to 50 | 2 |
50 to 100 | 4 |
100 to 200 | 6 |
200 to 500 | 8 |
500 to 1000 | 10 |
over 1000 | 16 |
#Bitmap restricts the size of the data slot pool. The maximum number of slots in a data slot pool is determined by multiplying #BITMAP by 2048.
#BITMAP= *none
The specification of the number of bitmaps is omitted.
#BITMAP=<integer 1..32>
Number of bitmaps for administering each data slotpool.
RETRY=...
This operand controls the behavior for abnormal termination of BCAM.
RETRY= *none
No specification is made on the behavior after abnormal BCAM termination.
Default: NO
RETRY=ABNORMAL
In the event of abnormal termination of BCAM, a restart is carried out using the operands of the last DCSTART command.
RETRY=NO
No restart is carried out in the event of abnormal termination of BCAM.
INI=...
Specifies the initialized objects.
The INI operand only has an affect on the objects defined in an RDF.
INI= *none
The specification of which objects are initialized is omitted (corresponds to INI=ONLY).
INI=ONLY
Only the host is initialized.
ACT=...
Specifies the activated objects.
The ACT operand only has an affect on the objects defined in an RDF.
ACT= *none
The specification of which objects are to be activated is omitted.
ACT=NO
No objects are activated.
ACT=YES
Only those objects that have also been initialized are activated.
ACT=ONLY
Only the host is activated.
INI=LOCAL
All LAN nodes are initialized.
ACT=...
Specifies the activated objects.
The ACT operand only has an affect on the objects defined in an RDF.
ACT= *none
The specification of which objects are to be activated is omitted (corresponds to ACT=YES).
ACT=NO
No objects are activated.
ACT=YES
Only those objects that have also been initialized are activated.
ACT=ONLY
Only the host is activated.
ACT=LOCAL
All LAN nodes are activated.
INI=NODE
All LAN nodes , as well as all processors directly connected to the LAN, are initialized.
ACT=...
Specifies the activated objects.
The ACT operand only has an affect on the objects defined in an RDF.
ACT= *none
The specification of which objects are to be activated is omitted (corresponds to ACT=YES).
ACT=NO
No objects are activated.
ACT=YES
Those objects which were initialized are also activated.
ACT=ONLY
Only the host is activated.
ACT=LOCAL
All LAN nodes are activated.
ACT=NODE
All LAN nodes , as well as all processors directly connected to the LAN, are activated.
INI=ALL
All LAN nodes , all processors directly connected to the LAN, as well as all processors which can be accessed via the above named processor, are initialized.
ACT=...
Specifies the activated objects.
The ACT operand only has an affect on the objects defined in an RDF.
ACT= *none
The specification of which objects are to be activated is omitted.
ACT=NO
No objects are activated.
ACT=YES
Those objects which were initialized are also activated (corresponds to ACT=YES).
ACT=ONLY
Only the host is activated.
ACT=LOCAL
All LAN nodes are activated.
ACT=NODE
All LAN nodes , as well as all processors directly connected to the LAN, are activated.
ACT=ALL
All LAN nodes , all processors directly connected to the LAN, as well as all processors which can be accessed via the above named processor, are activated.
APPLICATION-TABLE=...
Relevant for applications which do not run on the standard host.
APPLICATION-TABLE defines the SAM file (application file) which contains the assignment of applications to virtual hosts. The information from this file is transferred periodically to the BCAM tables, but only takes effect for the individual application when the application is terminated and restarted.
APPLICATION-TABLE= *none
No specifications for using the APPLICATION-TABLE.
The default name is used.
APPLICATION-TABLE=(...)
Specifications are made for using the application file.
FILE=...
Specifies the name of the application file. The file name mus always be cataloged in the home pubset, otherwise errors can occur in connection with files cataloged on data pubsets or shared pubsets.
FILE= *none
No specifications for the name of the application file.
In this instance the default name $TSOS.SYSDAT.BCAM.APPLICATIONS is used.
FILE=<filename 1..50>
Defines local filename for the application file.
The filename of BCAM is supplemented by a four-character suffix.
SOCKETHOST-TABLE=...
Only relevant for automatic end system creation.
SOCKETHOST-TABLE defines the SAM file (socket host file) which contains the assignment of socket host names to IP addresses. The information from this file is transferred periodically to the BCAM tables. ISOCKET calls, which request the conversion of socket host names to IP addresses and vice versa, access the BCAM tables.
SOCKETHOST-TABLE= *none
No specifications for using the socket host file.
The default name is used.
SOCKETHOST-TABLE=(...)
Specifications are made for using the socket host file.
FILE=...
Specifies the name of the socket host file. The file must always be cataloged in the home pubset, otherwise errors can occur in connection with files cataloged on data pubsets or shared pubsets.
FILE= *none
No specifications for the name of the socket host file.
In this instance the default name $TSOS.SYSDAT.BCAM.ETC.HOSTS is used.
FILE=<filename 1..50>
Defines local filename for the socket host file.
The filename of BCAM is supplemented by a four-character suffix.
PROCESSOR-TABLE=...
Only relevant for automatic end system creation.
PROCESSOR-TABLE defines the SAM file (processor file) which contains the assignment of processor names to network addresses. ACCESS=UPDATE/READ/ALLOW is used to control automatic end system creation.
PROCESSOR-TABLE= *none
No specifications for using the processor file.
The default name is used.
PROCESSOR-TABLE=(...)
Specifications are made for using the processor file.
FILE=...
Specifies the name of the processor file. The file name must always be cataloged in the home pubset, otherwise errors can occur in connection with files cataloged on data pubsets or shared pubsets.
FILE= *none
No specifications for the name of the processor file.
In this instance the default name $TSOS.SYSDAT.BCAM.PROCESSORS is used.
FILE=<filename>
Defines a local filename for the processor file.
The filename of BCAM is supplemented by a four-character suffix.
ACCESS=...
Controls the scope of automatic end system creation. A detailed description of this operand is provided in the section "Processor file".
ACCESS= *unchanged
No specification is entered for controlling automatic end system creation.Default: UPDATE
ACCESS=UPDATE
Any partner end system may be created.
ACCESS=ALLOW
Any partner end system may be created, but not created in the files which are assigned to the processor file.
ACCESS=READ
The partner end systems which have the specified processor names and are described in the processor file may be created.
FQDN-TABLE=...
FQDN-TABLE defines the SAM file containing the assignment of FQDN to BCAM names and/or IP addresses. The information from this file (FQDN file) is transferred periodically to the BCAM tables.
FQDN-TABLE= *none
The use of the FQDN file is not specified.
The default name is used.
FQDN-TABLE=(...)
Specifies how the FQDN file is used.
FILE=...
Specifies the name of the FQDN file. The file name must be cataloged on the home pubset. Errors may occur in connection with files which are cataloged on data pubsets or shared pubsets.
FILE= *none
The name of the FQDN file is not specified.
In this case the default name $TSOS.SYSDAT.BCAM.FQDN is used.
FILE=<filename 1..50>
Defines an own file name for the FQDN file.
The file name of BCAM is supplemented by a four-character suffix.
SERVICES-TABLE=...
Defines a new SAM file containing the assignment of services to port numbers. The information from this file (services file) is transferred periodically to the BCAM tables.
SERVICES-TABLE= *unchanged
SAM file containing the assignment of services to port numbers is not specified.
SERVICES-TABLE=(...)
SAM file containing the assignment of services to port numbers.
FILE=...
Specifies the name of the SAM file containing the assignment of services to port numbers.
The file name must be cataloged on the home pubset. Errors may occur in connection with files which are cataloged on data pubsets or shared pubsets.
Default name: $TSOS.SYSDAT.BCAM.ETC.SERVICES
The file name is compared with the file names of other BCAM tables which have also been entered or are already available to prevent this file being assigned to more than one BCAM table.
FILE= *unchanged
The name of the SAM file containing the assignment of services to port numbers is not specified.
FILE=<filename 1..50>
Name of the SAM file containing the assignment of services to port numbers.
The file name of BCAM is supplemented by a four-character suffix.
MAX-ISAM-POOL-SIZE=...
MAX-ISAM-POOL-SIZE defines the maximum size of the ISAM pool (specified in PAM pages) for the auxiliary ISAM files of the BCAM control files (application file, processor file, socket host file, FDQN file, and services file).
MAX-ISAM-POOL-SIZE=*unchanged
You do not specify the absolute size of the ISAM pool.
MAX-ISAM-POOL-SIZE=*STD
The size of the ISAM pool is set to the default value of 1536 PAM pages..
MAX-ISAM-POOL-SIZE=<integer 128..32766>
Maximum size of the ISAM pool (specified in PAM pages)
MAX-SLOT-PAGES =
MAX-SLOT-PAGES defines the maximum size in pages of the control block pool.
MAX-SLOT-PAGES = *UNCHANGED
You do not specify the maximum size of the control block pool.
MAX-SLOT-PAGES = *STD
The maximum size is to be changed to the default value (4608 pages).
MAX-SLOT-PAGES = <integer 2048 .. 65535>
Maximum size of the control block pool in pages.
MAX-DNS-ACC-ENTRIES=
You can define the number of entries for the management of the IP and IPv6 address ranges and for the processor’s namespace.
MAX-DNS-ACC-ENTRIES = *unchanged
You leave the number of entries for the management of the IP and IPv6 address ranges and for the processor’s namespace unchanged.
Default: 4096
MAX-DNS-ACC-ENTRIES=<integer 0 .. 32766>
Number of entries for the management of the IP and IPv6 address ranges and for the processor’s namespace. The specification 0 causes the default value to be used.
MAX-VLAN-ASSIGNMENT-ENTRIES=...
You can define the number of entries for the management of the IP and IPv6 address ranges for assignment to a VLAN ID.
MAX-VLAN-ASSIGNMENT-ENTRIES = *unchanged
You leave the number of entries for the management of the IP and IPv6 address ranges for assignment to a VLAN ID unchanged.
Default: 1024
MAX-VLAN-ASSIGNMENT-ENTRIES=<integer 0 .. 32766>
Number of entries for the management of the IP and IPv6 address ranges for assignment to a VLAN ID. The specification 0 causes the default value to be used.
REASON=...
Specifies the reason for the error response defined in the ACTION operand.
The values can also be specified as a list (list-poss).
REASON= *none
No specification of the reason for the error response.
REASON=BS2-SS
The reason for the error response lies in the use of a BS2000 interface.
REASON=BOURSE-SS
The reason for the error response lies in the use of the BS2000 bourse interface.
REASON=TIMER-SS
The reason for the error response lies in the use of the BS2000 timer interface.
REASON=DEVICE-SS
The reason for the error response lies in the use of the BS2000 device interface.
REASON=SIGNAL-SS
The reason for the error response lies in the use of the BS2000 signal interface.
REASON=CONTINGENCY-SS
The reason for the error response lies in the use of the BS2000-CONTINGENCY interface.
REASON=SLOTPOOL-SS
The reason for the error response lies in the use of the BS2000 slotpool interface.
REASON=TASK-SS
The reason for the error response lies in the use of the BS2000 task interface.
REASON=USER-TIMEOUT
The reason for the error response is a timeout while waiting for the user call to be processed under BCAM task.
REASON=MEMORY-SS
The reason for the error response lies in the use of the BS2000 memory interface.
ACTION=...
Defines the action to be taken in response to the errors specified with REASON.
The values can also be specified as a list (list-poss).
ACTION= *none
No error response is switched on.
ACTION=DUMP
A dump is created (in the event of an error return code).
ACTION=MSG
Message BCA0777 is generated (even if the return code is ok).
REMOTE-IP-NSDU=...
Defines the NSDU length for IP routes, which operate via at least one router.
REMOTE-IP-NSDU=*UNCHANGED
The NSDU length for remote IP routes remains unchanged.
REMOTE-IP-NSDU=*STD
The NSDU length for remote IP routes is set to the default value (556 bytes) in accordance with RFC1122.
REMOTE-IP-NSDU=<integer 512..65530>
The NSDU length for remote IP routes is set to the specified value.
SOFTIME=...
Monitoring period for processing of the SOF in seconds.
1 ... 600 ...2147483
CMDFILE-CONTINUATION=...
CMDFILE-CONTINUATION is used to specify for which command processing results the SOF or BCAM command file is further processed.
CMDFILE-CONTINUATION= *unchanged
The current setting of the command processing results that determine when the SOF is further processed is not changed.
Default: POSITIVE-RESULTS
CMDFILE-CONTINUATION=ALL-RESULTS
The SOF is further processed, regardless of the command processing results.
CMDFILE-CONTINUATION=POSITIVE-RESULT
The SOF is further processed only for positive command processing results.
CMDFILE-CONTINUATION=NEGATIVE-RESULT
The SOF is further processed only for negative command processing results.