Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Create Device Description (APPC) (CRTDEVAPPC) command creates a device description for an Advanced Program-to-Program Communications (APPC) device.
Restriction: You must have input/output system configuration (*IOSYSCFG) special authority to use this command.
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
DEVD | Device description | Name | Required, Positional 1 |
RMTLOCNAME | Remote location | Communications name | Required, Positional 2 |
ONLINE | Online at IPL | *YES, *NO | Optional |
LCLLOCNAME | Local location | Communications name, *NETATR | Optional |
RMTNETID | Remote network identifier | Communications name, *NETATR, *NONE | Optional |
CTL | Attached controller | Name | Optional |
MODE | Mode | Values (up to 14 repetitions): Communications name, *NETATR | Optional |
MSGQ | Message queue | Single values: *CTLD, *SYSOPR Other values: Qualified object name |
Optional |
Qualifier 1: Message queue | Name, QSYSOPR | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
APPN | APPN-capable | *YES, *NO | Optional |
SNGSSN | Single session | Single values: *NO Other values: Element list |
Optional |
Element 1: Single session capable | *YES | ||
Element 2: Number of conversations | 1-512, 10 | ||
LCLCTLSSN | Locally controlled session | *NO, *YES | Optional |
PREESTSSN | Pre-established session | *NO, *YES | Optional |
LOCPWD | Location password | Character value, *NONE | Optional |
SECURELOC | Secure location | *NO, *YES, *VFYENCPWD | Optional |
TEXT | Text 'description' | Character value, *BLANK | Optional |
LOCADR | Local location address | 00-FF, 00 | Optional |
AUT | Authority | Name, *CHANGE, *ALL, *USE, *EXCLUDE, *LIBCRTAUT | Optional |
Top |
Specifies the name of the device description.
This is a required parameter.
Top |
Specifies the remote location name of the system with which this object communicates.
Top |
Specifies whether this object is automatically varied on at initial program load (IPL).
This device is varied on automatically at IPL.
This device is not varied on automatically at IPL.
Top |
Specifies the unique location name that identifies the local system to remote devices. The name cannot be the same as that specified for the Remote location (RMTLOCNAME) parameter. If the values specified on the Remote network ID and Local network ID parameters are the same, the combination of the names specified for the LCLLOCNAME parameter and the RMTLOCNAME parameter must be unique for each device description attached to the same controller.
Use the Display Network Attributes (DSPNETA) command to determine the default local location name.
Specify the local location name.
Top |
Specifies the name of the remote network.
The remote network name is X'40'.
Specify the ID of the remote network.
Top |
Specifies the name of the controller description to which this device is attached.
Note: To use this device for communicating with a remote location that resides on the same system as the local location, specify a controller description that was created with LINKTYPE (*LOCAL) specified.
Top |
Specifies the names of the modes that define the sessions on this device.
You can enter multiple values for this parameter.
Specify the name of mode descriptions used by this device. The mode name cannot be CPSVCMG or SNASVCMG; these mode names are reserved for system use.
Specify up to 14 mode names.
Top |
Specifies the message queue to which operational messages for this device are sent.
Specify the name of the message queue to which operational messages are sent.
All libraries in the job's library list are searched until the first match is found.
The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.
Specify the name of the library to be searched.
Top |
Specifies whether this device is for Advanced Peer-to-Peer Networking (APPN).
This device is for APPN.
This device is not for APPN.
Top |
Specifies whether a single or multiple sessions are used with remote locations. If single sessions are used, the number of conversations must be specified.
Single values
Multiple sessions are used.
Element 1: Single session capable
Single sessions are used.
Element 2: Number of conversations
The default number of conversations is 10.
Specify a valid value that ranges from 1 through 512 for the number of conversations.
Top |
Specifies whether the session is a locally controlled session.
The single session is remotely controlled.
The single session is locally controlled.
Top |
Specifies whether the session is established when the connection with the remote system is established.
The session is not established automatically at connection time.
The session is established automatically at connection time.
Top |
Specifies the password to be used to validate a connection.
There is no password.
Specify the password as a string of hexadecimal characters.
Top |
Specifies how security information is handled for program start requests received from remote systems. The value is sent to the remote system when sessions are established. It is used in determining how allocate or evoke requests should be built. The value only applies to conversations started with the SECURITY(SAME) level of security.
The remote system is not a secure location. Security validation done by the remote system is not accepted. SECURITY(SAME) conversations are treated as SECURITY(NONE). No security information will be sent with allocate or evoke requests.
The remote system is a secure location and the local system will accept security validation done by remote systems. For SECURITY(SAME) conversations, the local system allows the remote system to verify user passwords. On the remote system, user IDs are retrieved from the security manager. The user IDs are then sent with an already verified indicator in the allocate or evoke requests.
The remote system is not a secure location. For SECURITY(SAME) conversations, the remote system is not allowed to send the already verified indicator. On the remote system, user IDs and passwords are retrieved from the security manager. Passwords are then encrypted and sent with the user IDs in the allocate or evoke requests, to be verified by the local system. This value should only be used if the remote system is using V3R2M0 operating system or later. If the remote system does not support password protection then session establishment will not be allowed. For remote systems that support password protection, but do not support verification of encrypted passwords (VFYENCPWD), conversations will be treated as SECURITY(NONE).
Top |
Specifies the text that briefly describes the object.
Top |
Specifies the local location address for this device.
The possible values are 00 to FF.
Top |
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.
Top |
CRTDEVAPPC DEVD(APPC1) LOCADR(00) RMTLOCNAME(CHICAGO) CTL(CTLAPPC01) SNGSSN(*YES)
This command creates a device description for an APPC communications device named APPC1. The device has a location address of X'00' and is in Chicago, attached to controller CTLAPPC01. This device is limited to one session at a time.
Top |
*ESCAPE Messages
Top |