Customizing Messages

You can customize the messages users see during logon and application selection by modifying the gateway configuration member.

When exceptions are detected, the gateway generates message numbers. Once identified, the message number is used to locate the message text defined by the MESSAGE statement in the configuration member. If no MESSAGE statement is found to match the message number, a default message is provided. The VIGMSG variable is then replaced by the message text, and the panel is redisplayed.

Here is the format of the MESSAGE statement:

MESSAGE   msgnumber   [msg_identifier|'msg text']

msgnumber

The message number internally associated with an exception detected by a gateway. A description of the exceptions defined and the associated message numbers appears below.

Msg number Error or exception

00

An application has been selected, but the gateway configuration has changed. The user is given a chance to respecify his request.

01

The requested application does not match any authorized session ID defined in an application definition (APPLDEF), or is not included in the authorized application list (APPLIST) associated with the user.

02

HELP was requested, but no HELP is available. The HELP operand can be specified in the APPLDEF command that defines the application, or in the configuration definition for a specific data element.

03

A valid destination was selected, but the destination application is inactive or is not accepting logon requests.

04

An undefined logmode name was specified. For virtual sessions, make sure the LOGMODE parameter on the VSM command specifies a valid entry name. If the &VIGLMODE product variable is being used to supply the logmode name, make sure it contains the correct name.

05

The destination application rejected the session request because the logical unit was not known. For example, an attempt to start a session with IMS will generate this message if the LU name of the physical terminal for CLSDST PASS sessions or the virtual terminal for SINGLE sessions does not define a valid IMS PTERM.

06

The logical unit rejected the session request because of unsupported session parameters. For example, an attempt to bind a 3278 model 2 with a model 3 bind will generate this message.

07

Unable to establish a virtual terminal session.

08

The virtual terminal pool specified for a SINGLE session is empty.

09

The virtual printer pool specified for a SINGLE session is empty.

10

The name of the application list is not found. No APPLIST command matches the name specified in the APPLIST data element.

11

Gateway setup error. A gateway configuration contains inconsistent definitions. This occurs, for example, if the IMS ASSIGN session service is selected but the LTERM data element is not defined as part of the configuration.

12

An unsupported command or function key was entered.

13

The printer terminal identified by the PRTNODE data element could not be acquired.

14

A virtual printer terminal session could not be established.

15

No IMS operator session is active with the required IMS subsystem. When either the ASSIGN or the DEQUEUE session service is selected, a virtual IMS master terminal (MTO) operator session must be available.

16

An undefined LTERM name has been specified. The name associated with the LTERM data element is not defined in the IMS/DC gen.

17

An undefined PTERM name has been specified. The logical unit name of the VTAM terminal is not defined in the IMS/DC gen. If terminal pooling is being used, this name will be the LU name of the virtual terminal.

18

The requested LTERM is not available. The LTERM is a valid LTERM name, but the ASSIGN command could not assign this LTERM to the session.

19

The STOP NODE command failed. This command is issued by a virtual MTO session.

20

The DEQUEUE NODE command failed. This command is issued by a virtual MTO session.

21

The RESTART NODE command failed. This command is issued by a virtual MTO session.

22

The START NODE command failed. This command is issued by a virtual MTO session.

23

The requested LTERM is in use. This message can occur if the specified LTERM is already in an active session, and the Extended LTERM Verification (XLV) option is requested.

24

No authorized applications.

25

Resolution limit exceeded.

msg_identifier

A character string beginning with the characters SMSGGW and containing no imbedded blanks. The message identifier is defined in a dialog named KLSMSGGn (where n is a 1-digit national language identifier).

msg text

A valid string expression up to 255 characters in length, to notify the user of the problem or exception.