Resolving DFH4103, DFH4104, DFH4110 and DFH4111 messages in Ideal for Datacom

Products

• Datacom
• DATACOM - AD
• Ideal
• Datacom/AD
• Datacom/Server
• Datacom/DB

Issue/Introduction

Resolving DFH4103, DFH4104, DFH4110 and DFH4111 messages in Ideal for Datacom

Environment

Release: Ideal for Datacom

Resolution

There are some parameter definitions in the CICS System Initialization Table (DFHSIT) that may cause CICS messages to be received during an Ideal for Datacom session. These parameters are used for CICS Basic Mapping Support (BMS=YES in DFHSIT) and are set equal to a two-byte character string. If one of these character strings is typed into an unprotected field during an Ideal session, a CICS message will be received upon hitting the ENTER key. However, this string must be the first two characters of the input stream from the terminal for this to occur. These strings are not being parsed by SCF but rather by CICS. You can return to the Ideal session via the CLEAR, PA1 or PA3 keys.

DFHSIT PARAMETER	IBM DEFAULT STRING	followed by	CICS MESSAGES
PGCHAIN	X/	blank/ non- blank	DFH4103 - ATTEMPTING TO PURGE, COPY OR CHAIN, BUT NO PAGES CURRENTLY CONNECTED TO THIS TERMINAL.
PGCOPY	C/	blank/ non- blank	DFH4103 - ATTEMPTING TO PURGE, COPY OR CHAIN, BUT NO PAGES CURRENTLY CONNECTED TO THIS TERMINAL.
PGPURGE	T/	blank non- blank	DFH4111 - REQUESTED PAGE PURGING FUNCTION NOT VALID. DFH4103 - ATTEMPTING TO PURGE, COPY OR CHAIN, BUT NO PAGES CURRENTLY CONNECTED TO TERMINAL.
PGRET	P/	blank non- blank	DFH4110 - REQUESTED PAGE RETRIEVE FUNCTION NOT VALID. DFH4104 - NO PAGES TO BE DISPLAYED.

If any of these messages are received and the corresponding character string has NOT been entered, it is likely that the definition in the DFHSIT has been altered to a two-byte string other than the default.

If you MUST use a certain two-byte string in an unprotected field during an Ideal session, then you will need to change the parameter definitions in the DFHSIT to a two-byte string less likely to be used. You should avoid using strings such as '@I' or '//' because using these strings would prohibit the use of Ideal internal commands or the submission or creation of JCL, respectively.