
*** Last updated 7/2/96 ***

This Informational APAR contains information regarding a
PTF for X.25 connections and sample configurations. The
PTF is SF32653 for the 5763XC1 product.

The code in this PTF takes care of 3 problems in the X.25 PAD
connection sequence:

1) Some PAD's send NULL characters mixed in with ASCII data
   characters (and CA/400 uses STRING functions in looking at
   the received data).

2) Some PAD's generate X.3 PAD responses in 7 Bit even parity,
   even though we tell the PAD through the SET 21:0 command to
   ignore and do not generate parity. Based on information
   received from the field, some PAD providers are generating
   this even parity, others are not.

3) The group processing was not correctly processing the
   'Time-Out' conditions on a failure.

The code has been changed to do the following:

1) Mask null characters so that the STRING functions that
   occurs during GROUP processing do not need to change.

2) The code now will ignore the parity bit in response data
   coming back from the PAD. If the user wishes to check and
   look at the parity bit, then the following keyword needs
   to be set in the VDWAN section of the SYSTEM.INI file:

     UsePADParity = TRUE

3) The code now properly behaves on response time-out
   conditions within each group.

The code also now hooks into system hardware resources only
while the hardware is being used by CA/400. This may make it
easier for the user to run different PC communications
applications on the serial port hardware and modem, without
the need to un-install CA/400 SYSTEM.INI device drivers.

The following are some examples of connecting to various
PAD's on a per country basis. It should be STRONGLY NOTED
that these are samples taken at a particular point in time,
and are NOT guaranteed to work on every PAD. Customers
should still work with their network or PAD provider to get
complete information regarding PAD Setup, configuration,
and connection sequences. These examples are flows that
occur between a PC and the PAD after the modem to modem
connection has completed.


************************************************************

Connecting to AUSTRALIA :

PC                                   PAD
-----                                -------
         <-------------------------- AUSTPAC
SET 1:0,2:0,3;2,5:0,6:5 CR --------->
         <-------------------------- *
SET 7:0,12:0,19:0,21:0 CR --------->
         <-------------------------- *
XXXXXX-YYYYYYYYY DD  CR   --------->
         <-------------------------- COM

In the above example, the PAD 'prompts' the user via the
AUSTPAC string. The PC then sends the 1st set of X.3 PAD
Commands, and gets an asterisk '*' back to indicate that the
PAD is ready for the next command.

The PC sends the 2nd set of X.3 Commands, and gets another
asterisk. The PC then sends the X.25 Call command with an
indication of call user data to the PAD - the PAD makes an
X.25 call to the AS/400. If the AS/400 accepts the call,
then the PAD sends a 'COM' response to the PC.


************************************************************

Connecting to Germany:

PC                                   PAD
-----                                -------
         <-------------------------- NEXTEL:
NUI ABCDEFG CR---------------------->
         <-------------------------- password
XXXXXXXX CR------------------------->
         <-------------------------- active
SET 1:0,2:0,3:2,5:0,6:5,7:0 CR------>
         <-------------------------- PAD Prompt
SET 9:0,10:0,12:0,13:0,14:0 CR------>
         <-------------------------- PAD Prompt
SET 15:0,16:127,17:24,18:18 CR------>
         <-------------------------- PAD Prompt
SET 19:0,20:0,21:0,22:0 CR--------->
         <-------------------------- PAD Prompt
XXXXXXXXXXXXXXXX DD  CR   --------->
         <-------------------------- CONNECTED

In the above example, the PAD 'prompts' the user via
the NEXTEL: string. The PC then sends the X.25 USER
ID to the PAD, the PAD then prompts for an X.25
Password, and sends the string 'active' to the PC to
indicate that the user has logged on to the network
successfully. The PC sends the 1st set of X.3 Commands,
and gets a PAD prompt when the PAD is ready for the
next command. The PC sends the 2nd set of X.3 Commands,
and gets a PAD prompt when the PAD is ready for the
next command. The PC sends the 3rd set of X.3 Commands,
and gets a PAD prompt when the PAD is ready for the
next command. The PC sends the 4th set of X.3 Commands,
and gets a PAD prompt when the PAD is ready for the
next command.

The PC then sends the X.25 Call command with an indication
of call user data to the PAD - the PAD makes an X.25 call
to the AS/400. If the AS/400 accepts the call, then the
PAD sends a 'CONNECTED' response to the PC.


************************************************************


Connecting to Belgium:

PC                                   PAD
-----                                -------
. CR ------------------------------->
     <------------------------------ RTT
XXXXXXXX CR------------------------->
         <-------------------------- active
SET 1:0,2:0,3:2,5:0,6:5,7:0 CR------>
         <-------------------------- *
SET 9:0,10:0,12:0,13:0,14:0 CR------>
         <-------------------------- *
SET 15:0,16:127,17:24,18:18 CR------>
         <-------------------------- *
SET 19:0,20:0,21:0,22:0 CR--------->
         <-------------------------- *
XXXXXXXXXXXXXXXX DD  CR   --------->
         <-------------------------- CONNECTED

In the above example, the PC sends 1st. It sends the
period ('.') followed by a Carriage Return. When the
PAD sees this, it then send the RTT prompt.

The PC sends the 1st set of X.3 Commands, and gets a
PAD prompt when the PAD is ready for the next command.
The PC sends the 2nd set of X.3 Commands, and gets a
PAD prompt when the PAD is ready for the next command.
The PC sends the 3rd set of X.3 Commands, and gets a
PAD prompt when the PAD is ready for the next command.
The PC sends the 4th set of X.3 Commands, and gets a
PAD prompt when the PAD is ready for the next command.

The PC then sends the X.25 Call command with an
indication of call user data to the PAD - the PAD makes
an X.25 call to the AS/400. If the AS/400 accepts the
call, then the PAD sends a 'CONNECTED' response to
the PC.


************************************************************


Connecting to ISRAEL:

PC                                   PAD
-----                                -------
@    ------------------------------->
    (wait 1 second )
. CR  ------------------------------>
    <------------------------------- TERMINAL=
D1 CR ------------------------------>
    <------------------------------- *
SET 1:0,2:0,3:2,5:0,6:5,7:0 CR------>
         <-------------------------- *
SET 9:0,10:0,12:0,13:0,14:0 CR------>
         <-------------------------- *
SET 15:0,16:127,17:24,18:18 CR------>
         <-------------------------- *
SET 19:0,20:0,21:0,22:0 CR--------->
         <-------------------------- *
XXXXXXXXXXXXXXXX DD  CR   --------->
         <-------------------------- CONNECTED

In the above example, the PC sends the ampersand ('@'),
then delays a second (this delay can be accomplished by
having the PC wait for a string that should not occur
.. e.g.,'dummyresponse').

The PAD then sends the 'TERMINAL=' Prompt. The PC responds
with a 'D1' Terminal type, and the PAD then prompts for
the next PAD command with an asterisk.

The PC sends the 1st set of X.3 Commands, and gets a PAD
prompt when the PAD is ready for the next command.
The PC sends the 2nd set of X.3 Commands, and gets a PAD
prompt when the PAD is ready for the next command.
The PC sends the 3rd set of X.3 Commands, and gets a PAD
prompt when the PAD is ready for the next command.
The PC sends the 4th set of X.3 Commands, and gets a PAD
prompt when the PAD is ready for the next command.

The PC then sends the X.25 Call command with an indication
of call user data to the PAD - the PAD makes an x.25 call
to the AS/400. If the AS/400 accepts the call, then the
PAD sends a 'CON' response to the PC.
