You use the DCSTART command to start the data communication system in the BS2000 system. The definition stored in the RDF for the BS2000 system is transferred to the BCAM data structure. If a number of BS2000 systems exist in a network, the DCSTART command is entered for each of these systems.
First of all, the DCSTART command automatically initiates the opening of the following internal privileged applications of the BS2000 system:
$BCAMNET (application for remote batch processing, if used)
$CONSOLE (application for universal console)
$BCADNS4 (application for LWRESD operation IP)
$BCADNS6 (application for LWRESD operation IPv6)
The command sequence dcsof is then processed if it is specified in the DCSOF operand of the DCSTART command.
You can simultaneously enter and activate any group of systems.
You can control which messages are logged. The time required to start BCAM is reduced if only error messages are displayed.
With the DCSTART command, automatic monitoring of connection requests and warnings is initiated. In current operation
connection requests are timed out after 30 seconds if they were not accepted or rejected beforehand. The time setting can be changed with the help of the CONN operand of the BCTIMES command.
the activities defined with the BCEND or BCOUT commands are carried out 10 seconds after the commands have been entered. The time setting can be changed with the help of the WARN operand of the BCTIMES command.
Monitoring of incoming messages is not automatically initiated by the DCSTART command. If the incoming messages are to be deleted during operation after a specified number of seconds – provided they have not been collected already – you must issue the BCTIMES command and define the LETT operand accordingly.
Before the console message ’BCAM ACTIVE’ is displayed, the current values for MAXNPA, MAXNPT, MAXCNN, PAGMEM and RESMEM are output with message BCA08F8.
BS2000 console | BS2000 SDF command | Command/ SOF file | SNMP management | Parameter service |
x | x |
List of valid command sources
DCSTART | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DCSOF=...
DCSOF defines whether startup of BCAM is to take place with the help of a command file (Start Option File).
If the SOF is not cataloged under the TSOS ID, its fully qualified file name must be specified. The file name must always be cataloged in the home pubset, otherwise errors may occur in connection with files cataloged on data pubsets or shared pubsets.
If the DCSOF operand is used, BCAM accesses the SOF. The SOF must have been created previously; it contains all commands for the (automatic) startup of the data communication system. The first command (DCOPT) of the SOF has, as its operands, the optional operands of the DCSTART command. If you also enter one or more of the optional operands with the DCSTART command, the value defined for startup is overwritten for this operand in the DCOPT command.
DCSOF= *none
The specification of the name of the SOF file is omitted (see metasyntax).
HOST=<host-name 1..8>
HOST is the name of the BS2000 system. HOST must be specified in the DCSTART or DCOPT command.
DCRDF=...
Refers to the name of the file which contains the network description (RDF).
DCRDF=<filename 1..54>
Name of the RDF.
The fully qualified file name is to be specified if the RDF is not under the TSOS user ID. The file name must always be cataloged in the home pubset, otherwise errors may occur in connection with files cataloged on data pubsets or shared pubsets.
DCRDF=*NONE,...
When *NONE is specified, startup occurs without an RDF.
MAXTSDU=...
This operand describes the maximum receive message length for the host.
MAXTSDU=<integer 4096..65530>
Specification of the maximum message length in bytes.
Default: 4096
DCSOF=<filename 1..54>
Name of the SOF with which the communication system is initialized. The first command of this SOF must be DCOPT.
HOST=...
HOST is the name of the BS2000 system for which BCAM was generated in the RDF. HOST must have been specified in the DCSTART or DCOPT command.
HOST= *none
The specification of the host name is omitted (see metasyntax).
HOST=<host-name 1..8>
Host name of the communication system.
DCRDF=...
Refers to the name of the file which contains the network description (RDF).
DCRDF= *none
The specification of the use of the RDF is omitted.
Default: $TSOS.DCRDF
DCRDF=<filename 1..54>
Name of the RDF.
The fully qualified file name is to be specified if the RDF is not 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. LWRESD may be started only after BCAM has been started.
JV-READY=...
Name of the job variable in which the BCAM operating mode 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 BCAM0716). If no job variable is available, no logging of the BCAM state by BCAM takes place.
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 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-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 being operated without RDF (RDF-less operation).
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, 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>
Defines the 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 files cataloged on data pubsets or shared pubsets.
JV-BCAM-STATUS=...
Name of the job variables in which the current BCAM status is entered (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 status 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
The specification of the number of applications that are not predefined is omitted.
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=...
Defines 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) can only be occupied by privileged applications. Privileged applications are those which run under the TSOS or NET-ADMINISTRATION BS2000 system privileges.
PRIVPORT#= *none
The 2050 value set as the default by BCAM remains unchanged.
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 occupy dynamically for an application. If SNMP-AGENTS is used on this computer, the port number 3161 is assigned for internal BCAM communication between master and subagents.
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#, then PRIVPORT# is set to the specification of FREEPORT#.
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 is always output for directly addressed systems (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 and 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 slot pool. 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
No specifications for the number of bitmaps.
#BITMAP=<integer 1..32>
Number of bitmaps for administering each data slot pool.
START=...
START specifies the operands selected for BCAM startup.
START=NEW
The valid start operands result from the sum of the currently used DCSTART command with START=NEW and the DCOPT command from the command file specified in the DCSOF operand. They can be changed in a command file or manually by means of a BCMOD command.
START=RETRY
BCAM is started with the operands which were valid at the last session start.
Details of the settings after an IPL or a BCAM session start can be found in section "Operand settings".
RETRY=...
This operand controls the behavior for the abnormal termination of BCAM.
RETRY= *none
No specification is made on the behavior after abnormal BCAM termination.
Default: NO
RETRY=ABNORMAL
A retry is carried out in the event of abnormal termination of BCAM.
RETRY=NO
A restart is not carried out in the event of abnormal termination of BCAM.
INI=...
Specifies the initialized objects.
The INI operand only affects the objects defined in an RDF.
INI= *none
The specification of objects to be initialized is omitted (corresponds to INI=ONLY).
INI=ONLY
Only the host is initialized.
ACT=...
Specifies the activated objects.
The ACT operand only affects the objects defined in an RDF.
ACT= *none
The specification of objects 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 to be activated.
INI=LOCAL
All LAN nodes are activated.
ACT=...
Specifies the activated objects.
The ACT operand only affects the objects defined in an RDF.
ACT= *none
The specification of the objects 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.
INI=NODE
All LAN nodes , as well as all processors directly connected to the LAN, are to be initialized.
ACT=...
Specifies the activated objects.
The ACT operand only affects the objects defined in an RDF.
ACT= *none
The specification of the objects 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 affects the objects defined in an RDF.
ACT= *none
The specification of the objects 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.
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=...
Only relevant for applications which should 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 immediately to the ISAM file, but only takes effect for the individual application when the application is terminated and restarted.
APPLICATION-TABLE= *none
No specifications for using the application file.
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 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 application file.
In this instance the default $TSOS.SYSDAT.BCAM.APPLICATIONS is used.
FILE=<filename 1..50>
Defines a local file name for the application file.
Please note that the file name of BCAM is extended 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 immediately to the associated ISAM file. ISOCKET calls, which request the conversion of socket host names to IP addresses and vice versa, access data in the corresponding ISAM file.
SOCKETHOST-TABLE= *none
No specifications for using the socket host file.
SOCKETHOST-TABLE=(...)
Specifications are made for using the socket host file.
The default name is used.
FILE=...
Specifies the file name of the socket host 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 socket host file.
In this instance, the default name $TSOS.SYSDAT.BCAM.ETC.HOSTS is used.
FILE=<filename 1..50>
Defines a local file name of the socket host file.
Please note that the file name of BCAM is extended 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 on using the processor file.
The default name is used.
PROCESSOR-TABLE=(...)
Specifications are made on 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 may 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 1..50>
Defines a local name for the processor file.
Please note that the file name of BCAM is extended 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 FQDN-TABLE is not specified.
The default name is used.
FQDN-TABLE=(...)
Specifies how FQDN-TABLE is used.
FILE=...
Specifies the file name of FQDN-TABLE. 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 file name of FQDN-TABLE 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 FQDN-TABLE.
The file name of BCAM is supplemented by a four-character suffix.
SERVICES-TABLE=...
Only relevant for automatic end system creation.
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 SERVICE to a port number.
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-ENTRIE = *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 in REASON.
The values can also be specified as a list (list-poss).
ACTION= *none
No error response is to be 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.
Command logging
For reasons of compatibility, the processing acknowledgment is supplied in news BCA0763 if it is positive and in news BCA0762 if it is negative, followed by the message NBR0740. In addition, for positive acknowledgments, the messages BCA0703, BCA0758 and BCA089F may also appear.
A description of the error messages that can be issued during command processing is provided in the table below.
Command return codes
(SC2) | Maincode | Meaning |
| CMD0001 | Command successfully processed |
| BCA0777 | Acknowledgment of interface use |
| BCA0832 | Packet length for link procedure or line too small, default used |
| BCA0893 | SOF editing cancelled |
| BCA071B | DCOPT command not first command of the SOF |
| BCA071C | Host name neither in DCOPT or in DCSTART-command entered |
| BCA0768 | Syntax error in command |
| BCA0810 | BCAM already active |
| BCA0815 | BCAM is being started up |
| BCA0825 | Parameter HOST does not define a BCAM host |
| BCA0702 | TRACE was not initialized |
| BCA089B | internal memory bottle-neck in establishing connection to $CONSOLE |
| BCA089C | A command could not be sent to $CONSOLE |
| BCA071F | BCAM version incompatible with BS2000 version |
| BCA076E | Start process cancelled at position. |
| BCA082B | RDF format wrong |
| BCA0891 | Failure to establish connection to $CONSOLE |
| BCA0895 | No DCOPT command |
| BCA089A | Connection to $CONSOLE returned |
| BCA0814 | BCAM is being terminated abnormally |
| BCA0816 | BCAM is terminating |
| BCA0715 | The application can not be opened |
| BCA0766 | BCAM is not active |