Create Ctl Desc (BSC) (CRTCTLBSC)
| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Create Controller Description (BSC) (CRTCTLBSC) command creates a controller description for a binary synchronous communications (BSC) controller.
Restriction: You must have input/output system configuration (*IOSYSCFG) special authority to use this command.
| Top |
Parameters
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| CTLD | Controller description | Name | Required, Positional 1 |
| ONLINE | Online at IPL | *YES, *NO | Optional |
| CNN | Connection type | *NONSWTPP, *SWTPP, *MPTRIB | Optional |
| SNBU | Switched network backup | *NO, *YES | Optional |
| LINE | Attached nonswitched line | Name | Optional |
| SWTLINLST | Switched line list | Values (up to 64 repetitions): Name | Optional |
| APPTYPE | Application type | *PGM, *RJE, *EML | Optional |
| INLCNN | Initial connection | *DIAL, *ANS | Optional |
| CNNNBR | Connection number | Character value | Optional |
| LCLID | Local identifier | Character value, *NOID | Optional |
| RMTID | Remote identifiers | Values (up to 64 repetitions): Character value, *ANY, *NOID | Optional |
| RJEHOST | RJE host type | *RES, *JES2, *JES3, *RSCS | Optional |
| RJELOGON | RJE host signon/logon | Character value | Optional |
| TEXT | Text 'description' | Character value, *BLANK | Optional |
| DEV | Attached devices | Values (up to 32 repetitions): Name | Optional |
| PREDIALDLY | Predial delay | 0-254, 6 | Optional |
| REDIALDLY | Redial delay | 0-254, 120 | Optional |
| DIALRTY | Dial retry | 0-254, 2 | Optional |
| CMNRCYLMT | Recovery limits | Single values: *SYSVAL Other values: Element list |
Optional |
| Element 1: Count limit | 0-99, 2 | ||
| Element 2: Time interval | 0-120, 5 | ||
| AUT | Authority | Name, *CHANGE, *ALL, *USE, *EXCLUDE, *LIBCRTAUT | Optional |
| Top |
Controller description (CTLD)
This is a required parameter.
Specifies the name of the controller description.
| Top |
Online at IPL (ONLINE)
Specifies whether this object is automatically varied on at initial program load (IPL).
- *YES
The controller is automatically varied on at IPL.
- *NO
The controller is not automatically varied on at IPL.
| Top |
Connection type (CNN)
Specifies the type of connection on which this BSC controller is used.
Note: This value must match the value specified for the CNN parameter in the CRTLINBSC command.
- *NONSWTPP
Nonswitched point-to-point connection.
- *SWTPP
Switched point-to-point connection.
- *MPTRIB
Multipoint tributary connection.
| Top |
Switched network backup (SNBU)
Specifies whether the remote system modem has the switched network backup (SNBU) feature. The backup feature is used to bypass a broken nonswitched (leased line) connection by establishing a switched connection. To activate SNBU, you must change the controller description of the modem from nonswitched to switched by specifying *YES for the Activate swt network backup (ACTSNBU) parameter.
Note: If the modem model you are using is an IBM 386x, 586x, or 786x, you should not change the controller description. Instead, manually switch the modem to the unswitched mode, and manually dial the connection.
Both the local and remote modems must support the SNBU feature to perform a valid activation.
- *NO
- The remote system modem does not have the SNBU feature.
- *YES
The remote system modem has the SNBU feature.
| Top |
Attached nonswitched line (LINE)
Specifies the name of the nonswitched line to which this controller is attached. The line description must already exist.
Note: The associated line must be varied off before this command is entered. Specify this parameter for controllers attaching to an X.25 permanent virtual circuit (PVC).
| Top |
Switched line list (SWTLINLST)
Specifies the names of the switched lines to which this controller attaches. The line descriptions must already exist. Up to 64 switched line names can be specified.
- switched-line-name
Specify the names of up to 64 lines that are connected to this controller. The same line name can be used more than once. For each line name specified, a line description by that name must already exist.
| Top |
Application type (APPTYPE)
Specifies the application type used by this device.
Note: This value must match the value specified on the APPTYPE parameter in the CRTLINBSC command.
- *PGM
The application is a user-written program.
- *RJE
The application is BSC Remote Job Entry (RJE).
- *EML
The application is BSC 3270 Device Emulation.
| Top |
Initial connection (INLCNN)
Specifies the method used to establish a connection with this controller.
- *DIAL
The system initiates outgoing calls and answers incoming calls.
- *ANS
The connection is made by the IBM System i5 when it answers an incoming call from this controller. If a call is received from the remote controller and all necessary conditions are met, the incoming call is answered by the system.
For X.25 connections, the line attached to the controller requires switched virtual circuits (SVCs) configured on the LGLCHLE parameter of type OUT or BOTH(*SVCOUT or *SVCBOTH) for the connection to succeed.
The line can be changed using the Change Line Description (X.25) (CHGLINX25) command.
| Top |
Connection number (CNNNBR)
Specifies the telephone number to dial to connect to this controller.
- connection-number
Specify the connection number.
| Top |
Local identifier (LCLID)
Specifies the local ID used to identify the local system to the remote controller.
- *NOID
The local system sends a null identifier when communicating with the controller.
- local-id
Specify a local ID that is from 2 to 30 hexadecimal characters long and contains an even number of characters. The identifier cannot contain any BSC control characters.
The following guidelines are recommended to help ensure that the telephone connection is made to the correct BSC controller:
- The local ID should be a minimum of 4 characters.
- If the ID is only 4 characters, the first 2 and last 2 should be the same (example: F3F3 or 8484).
| Top |
Remote identifiers (RMTID)
Specifies the identifiers for remote BSC controllers. A maximum of 64 remote controller IDs can be specified.
- *ANY
The system accepts any identifier sent by the remote controller.
Note: This value is valid only when it is the last or the only value specified.
- *NOID
The local system accepts a null identifier sent by the remote system.
- remote-ID
Specify a remote controller ID that is from 2 to 30 hexadecimal characters long and contains an even number of characters. The identifier cannot contain any BSC control characters.
The following guidelines are recommended to help ensure that the phone connection is made to the correct BSC controller:
- The remote ID should be a minimum of 4 characters.
- If the ID is only 4 characters, the first 2 and last 2 should be the same (example: F1F1 or 8585).
| Top |
RJE host type (RJEHOST)
Specifies the subsystem type of the host to which RJE is connected.
- *RES
The host is RES (Remote Entry System).
- *JES2
The host is JES2 (Job Entry Subsystem 2).
- *JES3
The host is JES3 (Job Entry Subsystem 3).
- *RSCS
The host is RSCS (Remote Spooling Communications System).
| Top |
RJE host signon/logon (RJELOGON)
Specify up to 80 characters of text, enclosed in apostrophes, used as sign-on text for the RJE host system. This parameter is required only when APPTYPE(*RJE) is specified. Specify the sign-on information required by the host system.
| Top |
Text 'description' (TEXT)
Specifies the text that briefly describes the object.
- *BLANK
No text is specified.
- character-value
Specify no more than 50 characters of text, enclosed in apostrophes.
| Top |
Attached devices (DEV)
Specifies the names of the devices that are attached to this controller. The device descriptions must already exist.
The maximum number of devices that can attach to this controller is 32 if CNN is *MPTRIB, 24 if APPTYPE is *RJE, or 1 for all other cases.
| Top |
Predial delay (PREDIALDLY)
Specifies the time interval to wait (in 0.5 second intervals) before dialing a number.
- 6
The default value of 6 provides a 3-second delay.
- predial-delay
- Specify a value ranging from 0 to 254 units. Each unit represents 0.5 second. To indicate no delay, specify a value of 0.
| Top |
Redial delay (REDIALDLY)
Specifies the time interval to wait (in 0.5 second intervals) before re-dialing when the call attempt is unsuccessful.
- 120
- The default value of 120 provides a 60-second delay.
- redial-delay
- Specify a value from 0 to 254 units. Each unit represents 0.5 second. To indicate no delay, specify a value of 0.
| Top |
Dial retry (DIALRTY)
Specifies the number of re-dial attempts made by the system before considering the dialing unsuccessful.
- 2
- The default number of retries is 2.
- dial-retry
- Specify a value from 0 to 254 in 0.5-second intervals, for the number of times the dialing will be tried.
| Top |
Recovery limits (CMNRCYLMT)
Specifies the number of recovery attempts made by the system before an inquiry message is sent to the system operator. Also specifies the time (in minutes) that must elapse before the system sends an inquiry message to the system operator indicating that the recovery attempt count limit is reached.
Element 1: Maximum Recovery Limit
- 2
Two recovery attempts are made within the interval specified.
- *SYSVAL
- The value in the QCMNRCYLMT system value is used.
- count limit
Specify the number of second-level recovery attempts to be made. Valid values range from 0 through 99.
Element 2: Recovery Time Interval
- 5
The specified number of recovery attempts is made within a 5-minute interval.
- time-interval
Specify the time interval (in minutes) at which the specified number of second-level recoveries are attempted. Valid values range from 0 through 120. If the value specified for count-limit is not 0, the value 0 specifies infinite recovery.
More information on communication recovery is in the Communcations Management book, SC41-5406.
| Top |
Authority (AUT)
Specifies the authority you are giving to users who do not have specific authority for the object, who are not on an authorization list, and whose group profile or supplemental group profiles do not have specific authority for the object.
- *CHANGE
- The user can perform all operations on the object except those limited to the owner or controlled by object existence (*OBJEXIST) and object management (*OBJMGT) authorities. The user can change and perform basic functions on the object. *CHANGE authority provides object operational (*OBJOPR) authority and all data authority. If the object is an authorization list, the user cannot add, change, or remove users.
- *ALL
- The user can perform all operations except those limited to the owner or controlled by authorization list management (*AUTLMGT) authority. The user can control the object's existence, specify the security for the object, change the object, and perform basic functions on the object. The user also can change ownership of the object.
- *USE
- The user can perform basic operations on the object, such as running a program or reading a file. The user cannot change the object. Use (*USE) authority provides object operational (*OBJOPR), read (*READ), and execute (*EXECUTE) authorities.
- *EXCLUDE
- The user cannot access the object.
- *LIBCRTAUT
- The system determines the authority for the object by using the value specified for the Create authority (CRTAUT) parameter on the Create Library (CRTLIB) command for the library containing the object to be created. If the value specified for the CRTAUT parameter is changed, the new value will not affect any existing objects.
- name
- Specify the name of an authorization list to be used for authority to the object. Users included in the authorization list are granted authority to the object as specified in the list. The authorization list must exist when the object is created.
| Top |
Examples
CRTCTLBSC CTLD(BSC1) CNN(*SWTPP)
CNNNBR(1234567) LCLID(020202)
RMTID(*ANY) SWTLINLST(BSC1) INLCNN(*ANS)
This command creates a BSC controller on a switched line that accepts calls from any remote location.
| Top |
Error messages
*ESCAPE Messages
- CPF26BB
- Extended wireless controller member not changed.
- CPF26BC
- Extended wireless controller member not displayed.
- CPF26BD
- Entry for barcode group not removed from extended wireless controller member.
- CPF26BE
- Entry for PTC group not removed from extended wireless controller member.
- CPF26BF
- Program QZXCINZ terminated abnormally. See previous messages.
- CPF26B3
- Extended wireless line member not added.
- CPF26B4
- Extended wireless line member not changed.
- CPF26B5
- Extended wireless line member not displayed.
- CPF26B8
- Extended wireless controller member not added.
- CPF2716
- Controller description &1 not created.
| Top |