Frequently Asked Questions
TCP/IP AX3000 Terminal on AS/400 iSeries |
Does my AX3000 Support AS400/5250 Connections?
Impossible to Enter the AX3000 Set-Up
How to Change the Keyboard Type ( PC or AS/400)?
Using the 5250 Keyboard or the PC/AT Keyboard
SCREEN SESSIONS
No connection to the AS/400
Giving a Name to a Screen Session
Programming Function Keys?
How to Use the Rule Function?
PRINTER SESSIONS
Which Printer Protocol: PRT5250 or LPD?
Setting-Up a Printer with the PRT5250 Protocol
Setting-Up a Printer with the LPD protocol
What is the "Manufacturer Type and Model" Parameter?
How to set the Right Value to "Manufacturer Type and Model" Parameter
Connecting Specific Printers (industrial, barcode, etc.)
In event of Problem with PRT5250 Printing...
MISCELLANEOUS
Editing a TCP/IP trace on AS/400
If you haven't found your answer here please try the General FAQ page
To connect to an AS/400 the AX3000 must contain 5250 emulation firmware. (Described by the I52 descriptor).
With this option the AX3000 offers both session connection (tn5250 protocol) and printer connection (Prt5250 and LPD protocols).
To determine your AX3000's firmware revision (and to see if I52 is installed), click here for instructions.
If the I52 option is not listed, contact Axel for the firmware file and click here for more information about downloading firmware.
The AX3000 supports both a 5250 (122 keys) and a PC/AT keyboard (102/105 keys).
The keystroke to enter the set-up are:
- <Ctrl><Alt><Esc> with a
PC keyboard
- <Rest><Alt><SetUp>
with a 5250 keyboard (for certain keyboards, these keys must be released in the following order
<Alt>, <Rest> and <SetUp>)
If the AX3000 setting is not consistent (a PC keyboard is attached but a 5250 keyboard is declared, or vice versa), the keyboard won’t work (for example, it's impossible to enter the set-up). Then the keyboard type must be modified.
The AX3000 supports both a 5250 (122 keys) and a PC/AT keyboard (102/105 keys). The keyboard type is not auto-detected. So the keyboard type must be specified through the AX3000 Set-Up.
If the AX3000 setting is not consistent (a PC keyboard is attached but a 5250 keyboard is declared, or vice versa), the keyboard won’t work. A specific keystroke allows to dynamically modify the keyboard type.
This keystroke is <Ctrl><Alt><Shift><K> with a PC keyboard, and <Rest><Alt><K> with a 5250 keyboard
The following tables list the 5250 functions (moving the cursor, system functions, etc) and the Axel functions (entering the set-up, etc) accessed from a 5250 keyboard (122 keys) and a PC/AT keyboard (102/105 keys).
5250 Functions | 5250 Keyboard | PC/AT Keyboard |
Attention Back tabulation Clear end of field Clear all fields Cursor shape Duplication Enter Euro symbol Execute macro F1...F12 F13...F24 Fast left Fast right Field - Field + Field Exit Help Hexa Home of field New Line Print (local mode) Print (Print HOST mode) Record Macro Reset Roll Down Roll Up Rule System Request Tabulation |
<Attn> <> or <Shift><> <ErInp> <Alt><Clear> <Cursor> <Dup> <Enter> <Alt><E> <Exec> <F1>...<F12> <F13>...<F24> <Shift><¬> <Shift><®> <Field -> <Field +> <Field Exit> <Help> <Alt><Help> <Alt><Rule> <> <Rest><Alt><Print> <Print> <Record> <Rest> <Shift><↓> <Shift><↑> <Rule> <Shift><Attn> <> |
<Esc> or <Alt Gr><Pause> <Shift><Tab> <End> <Pause> <Alt Gr><F11> <Shift><Insert> <Enter> <Alt Gr><E> <Alt Gr><F5> <F1>...<F12> <Shift><F1>...<Shift><F12> <Shift><¬> <Shift><®> <-> (numpad) <+> (numpad) <Entr> (numpad) <Alt Gr><F1> <Alt Gr><F7> <Home> <Ctrl Right> <Ctrl><Alt><Prt Scr> <Prt Scr> <Alt Gr><F4> <Ctrl Left> <Page Up> or <Shift><↓> <Page Down> or <Shift><↑> <Alt Gr><F12> <Shift><Esc> or <Alt Gr><Prt Scr> <Tab> |
AXEL Functions | 5250 Keyboard | PC/AT Keyboard |
AX3000 Shutdown AX3000 Set-Up Disconnecting the session Sending data to the aux. port |
<Rest><Alt><Del> <Rest><Alt><SetUp> <Rest><Alt><D> <Alt right><F2> |
<Ctrl><Alt><Del> <Ctrl><Alt><Esc> <Ctrl><Alt><Shift><D> <Alt Gr><F2> |
Several causes may explain why the AX3000 can not establish a session to the AS/400.
"Connecting to..." is displayed
The session is automatically closed
or
The screens "flashes" and "Connecting to..." is displayed
Check the Terminal Name (DEVNAME) is not already in use.
As with an SNA terminal, a name can be associated with an AX3000 session. This name is negotiated by the AX3000 at the connection time.
Note: a unique name must be given to each session.
To associate a name with a session, enter the AX3000 Set-Up, select [Configuration]-[Terminal]-[Session X]. Within the displayed box, set the "Terminal Name (DEVNAME)" parameter.
If this name is left blank, a dynamic name will be given by the AS/400 (QPADEVxxx)
This modification will take effect at the next AX3000 connection (the current AX3000 session can be closed by pressing <Ctrl><Alt><Shift><D> or the AX3000 can be shutdown by pressing <Ctrl><Alt><Del>)
The Axel 5250 emulation allows function keys to be programmed. For example a series of keystrokes can be recorded and played back by pressing a single key.
The recorded data is stored in non-volatile memory so is not affected by switching off.
Recorded keystrokes can be assigned to any of the 24 function keys (<F1> to <F12> or <Shift><F1> to <Shift><F12>).
Reminder: on a PC keyboard, <Alt Gr><F4> and <Alt Gr><F5> are the <Memor> and <Exec> keys of a 5250 keyboard.
Programming a Function Key
To record a series of keystrokes proceed as follows:
- press <Alt Gr><F4> to set the record mode,
- press any one of the 24 function keys to which you want to
assign the sequence,
- type the key sequence you want to record,
- press <Alt Gr><F4> to exit the record mode.
Note: for each session there is a maximum of 127 keystrokes recordable. Each individual function key has a maximum of 63 keystrokes recordable.
Processing a key sequence
To execute a series of keystrokes that have been recorded:
- press <Alt Gr><F5> to set the Process mode,
- press the recorded function key,
- the key sequence is processed.
Deleting a Recorded Function Key
To delete a series of keystrokes proceed as follows:
- press <Alt Gr><F4> to set the record mode,
- press any one of the 24 function keys to which you want to
delete,
- press <Alt Gr><F4> to exit the record mode.
The "rule" function allows the cursor to be located easily among other characters. Three types of rules are available:
- cross: a horizontal line and a vertical line indicate the cursor location,
- horizontal: a horizontal line is displayed at the cursor line,
- vertical: a vertical line is displayed at the cursor column.
Press <Alt Gr><F12> to enable/disable the rule function from a 5250 session.
Note : with a 5250 keyboard press <Rule>.
Three auxiliary ports are provided by the AX3000 (2 serial and 1 parallel). Because these ports are independently controlled, up to three printers can be attached to the AX3000.
These printers can be controlled by one of two protocols: LPD or Prt5250.
Normally the Prt5250 protocol is preferred. (No printer declaration is needed at OS/400 level), but the LPD protocol allows the printer to be shared between different operating systems.
The PRT5250 Protocol:
The PRT5250 protocol (RFC 2877) is OS/400 oriented. We strongly recommend using this PRT5250 protocol.
A printer controlled by Prt5250 is seen a real Printer Device. (related command: CHGDEVPRT).
When the AX3000 is powered up, the AX3000 auxiliary ports associated with the PRT5250 protocol are automatically connected to the AS/400 through a telnet PRT5250 session. Then, the information of each auxiliary port (with the AX3000 Set-Up) is sent to the AS/400. The related printers are automatically created and enabled (no need to use the CHGDEVPRT command). A PRT5250 remains established until the AX3000 is powered-off.
Note: this protocol is also used by the IBM emulator: "Client Access".
For more information about the PRT5250 protocol, click here.
The LPD protocol:
This protocol (RFCs 1048 and related) is provided as a standard feature by major operating systems (Unix/Linux, NT, etc.). The main benefit of this protocol is an LPD printer can be shared by different operating systems. But LPD restrictions are:
- the printer must be manually added to OS/400,
- the printer is accessed through an outqueue (and not a device),
- the printer job manipulation is not fully supported.
A printer controlled by LPD is seen as an OUTQUEUE (related command: CHGOUTQ).
The AS/400 host establishes an LPD connection when a print job is sent to the associated OUTQUEUE. This connection is closed when the print job is completed. The disconnection releases the printer. Then this printer is available for other servers.
For more information about the LPD protocol, click here
Enter the AX3000 Set-Up and select [Configuration]-[Aux. Ports]-[xxx]. In the displayed box, set the "Associated Service" to "Prt5250", then select "Net Service Parameters" and press <Space>.
The displayed box allows the Prt5250 protocol to be customized . The following parameters must be set:
Note: when a new printer device is created, the Prt5250 connection is immediately established when the set-up is exited. But, when an existing printer device is modified, the modifications will take effect after the current printer session disconnection (enter the AX3000 set-up and select [Diagnostics]-[Connection State]-[Close]) of after the AX3000 is shutdown (use <Ctrl><Alt><Del>).
If the printer is accessed by a single AS/400, we recommend using the PRT5250 protocol. For more information, click here.
An LPD printer is set both at the AX3000 level and at the OS/400 level.
AX3000 Level:
An LPD printer can be configured with 3 parameters:
- an IP address (the AX3000’s IP address),
- an identifier for the auxiliary port (character string),
- an optional filter to pre-process the file before printing (but generally this processing is done at the operating system level).
Enter the AX3000 Set-Up and select [Configuration]-[Aux. Ports]-[xxx]. In the displayed box, set the "Associated Service" to "LPD", then select "Net Service Parameters" and press <Space>.
The displayed box allows to customize the LPD protocol. The following parameters must be set:
OS/400 Level:
Note: only an OUTQUEUE can be created but we advise to create first a Printer DEVICE. (The device itself will not be used, only its OUTQUEUE will be used).
Printer Device Creation (the DEVD parameter is the printer, other parameter value are always the same).
===> CRTDEVPRT DEVD(AXPRT01) DEVCLS(*VRT) TYPE(3812) MODEL(1) FONT(11) |
Outqueue Modification (to associate it with the AX3000 auxiliary port):
===> CHGOUTQ OUTQ(AXPRT01) RMTSYS(*INTNETADR) RMTPRTQ('PARALLEL') CNNTYPE(*IP) DESTTYPE(*OTHER) TRANSFORM(*YES) MFRTYPMDL(*NECP2) INTNETADR('192.168.1.240') |
Where:
The run the following command to start the outqueue:
===> STRRMTWTR OUTQ(AXPRT01) |
Whatever the selected printer protocol (Prt5250 or LPD), the printer is considered by OS/400 as an "OUTQUEUE type 3812" with the "Host Print Transform (TRANSFORM)" mode enabled.
The printer is handled by the AS/400 with the information given either by the PRT5250 protocol, either by the CHGOUTQ with the LPD protocol.
When the "Host Print Transform (TRANSFORM)" parameter is set to "YES", the AS/400 converts EBCDIC characters of the printer flow into ASCII characters. But sometimes this basic operation is not enough for a enhanced print function (attributes, fonts, etc.). Another parameter, "Manufacturer Type and Model" (MFRTYPMDL) allows to specify the printer driver.
A printer driver list is provided as a standard feature. (But when it's required, a customized driver can be created).
For more information about the printer driver selection, click here.
The "Manufacturer type and model (MFRTYPMDL)" indicates the selected printer driver. For more information, click here.
A printer driver list is provided as a standard feature. This list is regularly updated by IBM with the new OS/400 versions. From the OS/400 V4R4, the provided printer drivers fit in most of cases.
Note: if no provided printer driver is available for your printer, a "customized" printer driver can be created by running the RTVWSCST and CRTWSCST commands. For more information, please consult the IBM documentation: "Printer Device Programming" reference : SC41-5713-03
If you want to test only the printer connection (PRT5250 or LPD), we advise you, for this first step, to use the "*NONE" value.
If a specific printer is used (industrial, barcode, etc.) click here.
The following will help you to select the proper printer driver
IBM Site:
IBM gives an on-line list of the certified printers with the related "Manufacturer Type and Model".
Note: if this link is not valid, search on the IBM site:: "Support for Various ASCII Printers".
CHGDEVPRT Command:
This command allows the value of "Manufacturer Type and Model (MFRTYPMDL)" associated with a device to be seen and modified.
To get help, locate the cursor on "Manufacturer Type and Model"
field:
- press <F4> to get the printer driver list
- press <F1> to get a list where some printer
drivers are associate with printers (brandname and model)
Attention: when a PRT5250 printer is used, the printer configuration is set through the AX3000 Set-Up. Use only the CHGDEVPRT to get help.
Most of industrial printers use a language specifically designed by the manufacture itself. In this case, no printer driver is used. Printer commands are directly sent and we advise you to set "Manufacturer Type and Model (MFRTYPMDL)" to "*NONE".
If a problem occurs when the 5250 printer is established an error code is sent to the AX3000.
To establish why a Prt5250 session has been refused, enter the AX3000 Set-Up and select the menu [Diagnostics]-[Connections].
Within the displayed dialog box, select the REFRESH button and press <CR>. Read the information displayed for the printer port (AUX1, AUX2 or PARA). Note the error code at the end of the line:
If no information is displayed, double-check that the auxiliary port is correctly set
When the connection status continually cycles through CLOSED to CONNECT and there is no error number displayed at the end of the line, the device name is already used by another connection.
If the Prt5250 connection status is "Connected" and if the error code is:
I902: at the AS/400 level, the printer is correctly set and ready (this can be checked by the WRKWTR command). If the printer problem remains, check using following method that the AX3000 is able to send data to the printer: enter the AX3000 Set-Up, select [Configuration]-[Aux. Ports]-[xxx]. Within the displayed box, select the [TEST] button. A test printer banner should be printed.
Whatever the Prt5250 connection status, check the error code value. These are the main values (all possible errors are listed in the RFC 2877):
8903 (Device not valid for session) : the printer name is used for another connection.
8925 (Creation of device failed) : during the printer creation operation, at least one parameter is detected wrong (ex.: non-existing printer model).
8928 (Change of device failed) : during the printer modification operation (reconnection with different parameters), at least one parameter is detected wrong (ex.: non-existing printer model).
8930 (Message queue does not exist) : the message queue or its library doesn't exist.
AX01 (Terminal type not recognized) : the TERM variable (by default IBM-3812-1) associated with the AX3000 auxiliary port is not correct.
There is an OS/400 utility allows the network traffic between the AS/400 and a specific AX3000 to be recorded and the resultant TCP/IP trace emailed to Axel for investigation.
From a Platine, be ready to run the application you want to trace.
===> STRSST |
1. Start a service tool |
3. Work with communications trace |
F6 Start trace |
Configuration object . . . . . name of the TCP/IP line Buffer size . . . . . . . . . 4 Number of bytes to trace Beginning bytes . . . . . . *MAX |
7. IP address data |
Remote IP address . . . . . . xxx.xxx.xxx.xxx |
Then on the Platine, run the software you want to trace.
2=Stop trace |
6=Format and print trace |
Controller . . . . . . . . . . *ALL Data representation. . . . . . 3 Format RR, RNR commands . . . N Format Broadcast data . . . . N Format UI data only . . . . . N Format SNA data only. . . . . N Format TCP/IP data only . . . Y Format IPX data only. . . . . N Select Ethernet data. . . . . 3 |
IP address . . . . . . . . . . *ALL IP address . . . . . . . . . . *ALL Port . . . . . . . . . . . . . *ALL |
The trace is now edited. From a Windows box running "Client Access", transfer the spool file and send it by email to our support department.