Change ICF Device Entry (CHGICFDEVE)

Parameters

Keyword	Description	Choices	Notes
FILE	ICF communication file	Qualified object name	Required, Key, Positional 1
	Qualifier 1: ICF communication file	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
PGMDEV	Program device	Character value	Required, Key, Positional 2
RMTLOCNAME	Remote location	Communications name, SAME, REQUESTER	Optional, Positional 3
CMNTYPE	Communication type	ALL, APPC, ASYNC, BSCEL, FINANCE, INTRA, RETAIL, SNUF	Optional, Positional 4
DEV	Device	Name, SAME, LOC	Optional
LCLLOCNAME	Local location	Communications name, SAME, LOC, *NETATR	Optional
MODE	Mode	Communications name, SAME, NETATR	Optional
RMTNETID	Remote network identifier	Communications name, SAME, LOC, NETATR, NONE	Optional
FMTSLT	Format select	SAME, PGM, RECID, RMTFMT	Optional
APPID	Application identifier	Name, SAME, DEVD, *USER	Optional
BATCH	Batch activity	SAME, NO, *YES	Optional
HOST	Host type	SAME, DEVD, CICS, IMS, *IMSRTR	Optional
ENDSSNHOST	End session with host	SAME, RSHUTD, *TERMSELF	Optional
SPCHOSTAPP	Special host application	SAME, DEVD, NONE, FLASH	Optional
INZSELF	Initialize self	SAME, NO, *YES	Optional
HDRPROC	Header processing	SAME, SYS, *USER	Optional
MSGPTC	Message protection	SAME, YES, *NO	Optional
EMLDEV	Emulation device	Single values: NONE Other values: Element list*	Optional
	Element 1: Device type	*SAME, 3278, 3284, 3286, 3287, 3288, 3289
	Element 2: Data format	SAME, UNFORMAT, FIELD, EXTFIELD, *NOFIELD
CNVTYPE	Conversation type	SAME, SYS, USER, SRCPGM	Optional
BLOCK	Blocking type	Element list	Optional
	Element 1: Blocking type	SAME, DEVD, NONE, ITB, IRS, NOSEP, USER, SEP
	Element 2: Record separator, if *SEP	Hexadecimal value, X'1E', *SAME
RCDLEN	Record length	1-32767, SAME, DEVD	Optional
BLKLEN	Block length	1-32767, SAME, DEVD	Optional
TRNSPY	Transmit in transparent mode	SAME, DEVD, NO, YES	Optional
DTACPR	Compress and decompress data	SAME, DEVD, NO, YES	Optional
TRUNC	Truncate trailing blanks	SAME, DEVD, NO, YES	Optional
OVRFLWDTA	Overflow data	SAME, DISCARD, *RETAIN	Optional
GRPSEP	Group separator type	SAME, DEVD, EOT, DEV3740, *OFCSYS	Optional
RMTBSCEL	Remote BSCEL	SAME, DEVD, NO, YES	Optional
INLCNN	Initial connection	SAME, CTLD, DIAL, ANS	Optional

Top

ICF communication file (FILE)

Specifies the intersystem communications function (ICF) file that contains the ICF program device entry to be changed.

This is a required parameter.

Qualifier 1: ICF communication file

name: Specify the name of the ICF file.

Qualifier 2: Library

*LIBL: All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB: The current library is used to locate the ICF file. If no library is specified as the current library for the job, QGPL is used.
name: Specify the library where the ICF file is located.

Remote location (RMTLOCNAME)

Specifies the remote location name with which the program communicates.

*SAME: The remote location name does not change.
communications-name: Specify the name of the remote location with which your program communicates. When the program is running, only one program device name associated with each asynchronous (Async), binary synchronous communications equivalence link (BSCEL), or system network architecture upline facility (SNUF) remote location may be acquired to the file at any one time.

*REQUESTER: The name used to refer to the communication device through which the program is started is used. The target program always uses *REQUESTER as the remote location name in the ICF file to connect to the session that the source program uses to send the EVOKE request. *REQUESTER may be specified for only one program device entry.
*REQUESTER is valid only for a target system communication job. If it is specified in any other type of job, an escape message is sent when the program device is accessed.

Communication type (CMNTYPE)

Specifies the communications type that appears in the prompt.

*ALL: All parameters appear in the prompt.
*APPC: Only the advanced program-to-program communications (APPC) parameters appear in the prompt.
*ASYNC: Only the asynchronous communications (ASYNC) parameters appear in the prompt.
*BSCEL: Only the binary synchronous communications equivalence link (BSCEL) parameters appear in the prompt.
*FINANCE: Only the FINANCE parameters appear in the prompt.
*INTRA: Only the INTRA parameters appear in the prompt.
*RETAIL: Only the RETAIL parameters appear in the prompt.
*SNUF: Only the Systems Network Architecture upline facility (SNUF) parameters appear in the prompt.

Device (DEV)

Specifies the communications device that is used. The DEV parameter is applies only to advanced program-to-program communications (APPC) and System Network Architecture upline facility (SNUF) communications.

*SAME: The device name does not change.
*LOC: The device associated with the remote location is used.
name: Specify the name of a communications device associated with the remote location. If the device name is not valid for the remote location, an escape message is sent when the program device is acquired.

Local location (LCLLOCNAME)

Specifies the local location name.

*SAME: The local location name does not change.
*LOC: The local location name is the same as the remote location name.

*NETATR: The LCLLOCNAME value specified in the system network attributes is used.

communications-name: Specify the local location name associated with the program device. The local location name is specified only if you want to indicate a different specific local location name for the remote location. If the local location name is not valid, an escape message is sent when the program device is acquired.

Mode (MODE)

Specifies the mode name used. This parameter applies only to APPC communications.

*SAME: The mode name does not change.

*NETATR: The mode in the network attributes is used.

BLANK: A mode name consisting of 8 blank characters is used.
communications-name: Specify a mode name for the APPC communication device. If the mode is not valid for any combination of remote location device, local location, and remote network ID, an escape message is sent when the program device is acquired.

Format select (FMTSLT)

Specifies the type of record format selection used for input operations for all devices.

*SAME: The record format selection value does not change.

*PGM: The program determines record format selections. If an input (read) operation with a record format name is specified, that format is always selected. If a record format is not specified for the input operation, the default format (the first record format in the file) is always selected.

*RECID: The RECID keywords specified in the DDS for the file are used to do record selection. If there are no RECID keywords in the file, an error message is sent, the acquire operation of the program device ends, and the device is not acquired.
*RMTFMT: The remote format names received from the sending system are used to do record selection. If the device is not an APPC device and *RMTFMT is specified, a run time error occurs at the time the program device is acquired.

Application identifier (APPID)

Specifies (in characters) the Virtual Telecommunications Access Method (VTAM) identifier of the Costumer Information Control System for Virtual Storage (CICS/VS) or Information Management System for Virtual Storage (IMS/V) host subsystem sent with the sign-on message. This parameter applies only to SNUF communications.

*SAME: The application ID does not change.
*DEVD: The application identifier specified in the device description is used.
*USER: The application program can send messages or a logon to the host. This is valid only when using the 3270 program interface.
name: Specify an application identifier. The specified application identifier is sent with the sign-on message.

Batch activity (BATCH)

Specifies, for both Customer Information Control System for Virtual Storage (CICS/VS) and Information Management System for Virtual Storage (IMS/VS), whether this session is used for batch jobs. This parameter applies to SNUF, INTRA, and RETAIL communications.

*SAME: The value does not change.
*NO: Batch jobs do not occur.
*YES: Batch jobs occur and SNUF does not assemble physical records into logical records. If *YES is specified, *NO must be specified for the Message protection (MSGPTC) parameter.

Host type (HOST)

Specifies the host or remote subsystem with which this session is communicating. This parameter applies only to SNUF communications.

*SAME: The value does not change.
*DEVD: The host system specified in the device description is used.
*CICS: The session communicates with Customer Information Control System for Virtual Storage.
*IMS: The session communicates with Information Management System for Virtual Storage.
*IMSRTR: The session communicates with IMS/VS by using the ready-to-receive option.

Header processing (HDRPROC)

Specifies, for both Customer Information Control System for Virtual Storage (CICS/VS) and Information Management System in Virtual Storage (IMS/VS), whether received function management headers are passed to the application program. This parameter applies to the SNUF communications type only.

*SAME: The value does not change.
*SYS: SNUF removes function management headers before passing data to the program.
*USER: Function management headers are passed to the program.

Message protection (MSGPTC)

Specifies, for both Customer Information Control System for Virtual Storage (CICS/VS) and Information Management Storage for Virtual Storage (IMS/VS), whether message protection is used for this session. This parameter applies only to SNUF communications.

*SAME: The value does not change.
*YES: Message protection is used. SNUF saves messages until you respond to them, and tries synchronization again if additional errors occur. *YES is valid only when *NO is specified for the Batch activity (BATCH) parameter.
*NO: Message protection is not used.

Emulation device (EMLDEV)

Specifies that this program device entry is used to send and receive 3270 data streams. The emulation device parameter consists of an emulation device type and an emulation device data format. The emulation device data format specifies the format of the type 3270 data stream being sent or received. A 20- or 32-byte common header that contains type 3270 command and data flow information is located at the start of the I/O buffer that is sending or receiving the type 3270 data stream. This parameter applies only to SNUF communications. This parameter can be specified as a list of two values (elements) or as a single value (*NONE).

Single values

*NONE: This program device entry is not used to send and receive 3270 data streams.

Element 1: Device type

*SAME: The emulation device does not change.
*NONE
3278: The data stream is for a 3278 or 3277 display device.
3284: The data stream is for a 3284 printer device.
3286: The data stream is for a 3286 printer device.
3287: The data stream is for a 3287 printer device.
3288: The data stream is for a 3288 printer device.
3289: The data stream is for a 3289 printer device.

Element 2: Data format

*SAME: The emulation device data format does not change.
*UNFORMAT: An unformatted 3270 data stream is sent or received. The user application program must translate the data stream into a display or printer image.
*FIELD: A formatted 3270 data stream is sent or received. The formatted 3270 data stream contains a display or printer image that contains field definitions. The field definitions indicate the location and characteristics of fields. *FIELD is valid only if *NO is specified for the Batch activity (BATCH) parameter.
*NOFIELD: A formatted 3270 data stream is sent or received. The formatted 3270 data stream contains a display or printer image without field definitions. *NOFIELD is valid only if *NO is specified for the BATCH parameter.
*EXTFIELD: A formatted 3270 data stream is sent or received. The formatted 3270 data stream contains a display or printer image followed by field definitions. The field definitions indicate the location and characteristics of fields. *EXTFIELD is valid only if *NO is specified for the BBATCH parameter and 3278 is specified for the device type on this parameter.

Conversation type (CNVTYPE)

Specifies the conversation type for which the application program is designed. This parameter applies only to advanced program-to-program communications (APPC).

*SAME: The value does not change.
*SYS: The system gives the length and general data stream identifier values that precede each section of user data in the APPC device protocol. For the LU 6.2 architecture, this is the mapped conversation support.
*USER: The application program gives the length and general data stream identifier values that precede each section of user data in the APPC device protocol. For the LU 6.2 architecture, this is the basic conversation support.
*SRCPGM: The target program accepts the conversation type specified by the source program.

Blocking type (BLOCK)

Specifies whether the system or the user controls how records are combined into blocks when they are sent. This parameter is used only for BSCEL communications. With this parameter, you may specify one of the following conditions of record formatting:

No blocking or deblocking
User blocking or deblocking
System blocking with record separator characters
System blocking of fixed-length records

If you specify a parameter value other than *NONE or *USER, records are blocked as required by the system for output and are deblocked on input.

Element 1: Blocking type

*SAME: The value does not change.
*DEVD: The block option specified in the device description is used.
*NONE: Blocking or deblocking is not done by the system.
*ITB: The records are blocked or deblocked based on the location of an intermediate text block (ITB) control character.
*IRS: The records are blocked or deblocked based on the location of an interrecord separator (IRS) character. For input files, a record is delimited by locating the next IRS character. For output files, an IRS character is added after the record.
*NOSEP: No record separator character is contained in the transmission block sent to or received from the device. The system blocks and deblocks the records by using a fixed-length record, as specified in the DDS format specifications.
*USER: The program gives all control characters, including record separator characters, BSCEL framing characters, transparency characters, and so forth, necessary to send records.
*SEP: The records are blocked or deblocked based on the location of a record separator character specified by the user. For input files, a record is delimited by locating the next record separator character. For output files, a record separator character is added after the record.

Element 2: Record separator, if *SEP

X'1E': The record separator character is a hexadecimal 1E.
*SAME: The value does not change.
hexadecimal-value: Specify a unique, 1-byte record separator character. The record separator character may be specified as 2 hexadecimal characters, as in BLOCK(*SEP FD) where X'FD' is the separator character.
Note: See the table in the description of the ADDICFDEVE command for more information about BSC control characters that cannot be used as record separator characters.

Record length (RCDLEN)

Specifies the maximum record length (in bytes) for data sent and received. This parameter applies only to SNUF and BSCEL communications.

*SAME: The value does not change.
*DEVD: The record length specified in the device description is used. If a record is longer than the specified record length, a run time error occurs at the time the record is sent or received.
1-32767: Specify the maximum allowed record length when this device file is used. If a record is longer than the specified record length, a run time error occurs at the time the record is sent or received. Valid values range from 1 through 32767 bytes for SNUF communications. For BSCEL communications, the maximum record length is 8192 bytes.

Block length (BLKLEN)

Specifies the maximum block length (in bytes) for data sent. This parameter applies only to BSCEL and SNUF communications.

*SAME: The block length does not change.
*DEVD: The block length specified in the device description is used.
1-32767: Specify the maximum block length of records sent when this device file is used. The value must be at least the size of the largest record sent. Valid values range from 1 through 32767 bytes for SNUF communications. For BSCEL communications, the maximum block length is 8192 bytes.

Transmit in transparent mode (TRNSPY)

Specifies whether data is sent in transparent text mode. Transparent text mode allows all 256 extended binary-coded decimal interchange code (EBCDIC) character codes to be sent. Use this function to send packed or binary data fields. This parameter applies only to BSCEL communications.

*SAME: The value does not change.
*DEVD: The text transparency option specified in the device description is used.
*NO: Text transparency is not used.
*YES: Text transparency is used, which permits the transmission of all 256 EBCDIC character codes. *YES is valid only when *NONE, *NOSEP, or *USER is specified for the Blocking type (BLOCK) parameter.
Note: Transparency of received data is determined by the data stream; therefore, this parameter is not relevant for received data. If TRNSPY(*YES) is specified with BLOCK(*USER), the BSCEL communications type ignores the transparency indicator during write operations. Correct controls must be given with the data to get transparent transmission of data. For example, the data-link escape (DLE) and start-of-text (STX) character control characters must first be specified; the system gives the remaining control characters for transparent sending of data.

Truncate trailing blanks (TRUNC)

Specifies whether trailing blanks are removed from output records. This parameter applies only to BSCEL communications.

*SAME: The value does not change.
*DEVD: The trailing blanks specified in the device description are used.
*NO: Trailing blanks are not removed from output records.
*YES: Trailing blanks are removed from output records.
Note: TRUNC(*YES) cannot be specified if BLOCK(*NOSEP) or BLOCK(*ITB) is specified. If TRUNC(*YES) is specified when DTACPR(*YES) or BLOCK(*USER) is specified, then truncation is ignored.

Group separator type (GRPSEP)

Specifies a separator for groups of data (for example, data sets and documents). This parameter applies only to BSCEL communications.

*SAME: The value does not change.
*DEVD: The group separator option specified in the device description is used.
*DEV3740: A null record (STXETX) is used as a data group separator.
*EOT: A block is sent that ends with the BSCEL end-of-transmission (EOT) control character used as a data group separator.
*OFCSYS: A block is sent that ends with the BSCEL end-of-information (ETX) control character is used as a data group separator.

Remote BSCEL (RMTBSCEL)

Specifies the type of BSCEL session with the remote system. This parameter applies only to BSCEL communications.

*SAME: The value does not change.
*DEVD: The RMTBSCEL option specified in the device description is used.
*NO: The remote system cannot recognize BSCEL commands or messages. In most cases, *NO is used when communicating with remote systems such as a 3741 Data Entry Station, an Office System 6, a 5230 Data Collection System, or a System/38.
*YES: The remote system recognizes the BSCEL transaction starting commands, transaction ending commands, and online messages. In most cases, *YES indicates that the remote system is another System i5, or a System/38, System/36, or System/34 with BSCEL support.

Examples

Example 1: Changing the Record Format Selection

CHGICFDEVE   FILE(ICFTEST)  PGMDEV(BSCEL2)
             RMTLOCNAME(BSCNYC)  FMTSLT(*RECID)

This command changes the program device entry named BSCEL2 in ICF file ICFTEST. The program device is changed to attributes of FMTSLT(*RECID). The remote location name is changed to BSCNYC.

Example 2: Changing the Conversation Type

CHGICFDEVE   FILE(QGPL/ICF1)  PGMDEV(APPC1)
             RMTLOCNAME(*REQUESTER)
             FMTSLT(*RMTFMT)  CNVTYPE(*SYS)

This command changes the program device entry named APPC1 in ICF file ICF1 to have the remote location name *REQUESTER. This program device entry is changed to the FMTSLT(*RMTFMT) and CNVTYPE(*SYS) attributes.

Example 3: Changing the Communications Device

CHGICFDEVE   FILE(ICFLIB/ICFAPPL1)  PGMDEV(APPC)
             RMTLOCNAME(APPCMPLS)  DEV(MPLSLINE2)

This command changes the program device entry named APPC in file ICFAPPL1. The remote location name is changed to APPCMPLS and the device is changed to MPLSLINE2.