Session ID

 

The session ID can be defined by a command line option or a resource.

The session ID can be a single value; for example “Smith". A set of session Ids can be defined; for example, Smith+n where n is 3 would make 3 session Ids available, “Smith1", “Smith2", and “Smith3".

Each 5250 session has a unique session ID. If a session ID is defined, it is used. If a session ID is not defined, default session IDs are defined, “A", “B", ….“Z", “AA", “AB",... If a user has one or more session IDs defined and already has 5250 sessions active using those session Ids, default session Ids are defined for subsequent 5250 sessions, starting with “A".

The 5250 session ID will be used by the following:

• 5250 window title: the default window title is the window title text, a colon, and the defined session ID. If a 5250 session has a default session ID, the target host systemand session number continue to be used in the 5250 window title.

• The DeskTop file stores the user's last 5250 window locations and font size. If a 5250 session has a defined session ID, this is used in the DeskTop file. If a 5250 session has a default session ID, the target host system and session number are used in the DeskTop file instead.

• The 5250 jump key can jump between all 5250 windows. The jump action can also have a session number as a parameter; for example, if jump(3) is defined as the action for a key sequence, this key sequence jumps to the third 5250 window. The jump action also allows a session ID as a parameter, for example, jump(“Smith").

• Color mapping allows a color map file to be stored for a specific 5250 session. If a 5250 session has a defined session ID, the session specific color mapping file applies to that session ID.

• Keyboard mapping allows a keyboard map file to be stored for a specific 5250 session. If a 5250 session has a defined session ID, the session specific keyboard map file applies to that session ID.

 

Parent topic:

X resources for the iSeries Access for Linux emulator