        This technical note documents configuring and using WinAPPC with the IBM S/36 or AS/36. Synapse has added support for the S/36 in release 3.22 and above of WinAPPC. In this document, all references to S/36 refer to both the S/36 and AS/36 systems. WinAPPC now supports concurrent connections to the AS/400 and the S/36 for display and printer emulation. File transfer is not supported nor planned for the S/36 system. Certain configuration features are unique to each system (AS/400 or S/36) and where different are limitations of the IBM provided support. All WinAPPC emulation product features, such as session preferences, ActionBar, Hotspots, font select/sizing are supported. Examine the advanced configuration options screens to review the available options for each system type.
When configuring NS/Router, no special considerations apply, except where to get the appropriate system configuration information, such as system name. Details of where the system name, PC location name, user ID and password are covered in the S/36 section below.
10.0 CNFIGSSP - COMMUNICATIONS LINE DEFINITION
1. Which line is being defined ................... 9
2. What type of line is it? ...................... 6
3. Automatic reconnect for the line? ............. Y
4. If line is X.25, enter X.25 member name........
10.1 CNFIGSSP - COMMUNICATIONS LINE DEFINITION
Source service access point (SSAP) value ...... 04
While I am not sure, I believe that SSP software features:
6001 - communications
6096 - APPN
LAN communations support
must be installed on the S/36. IBM should be able to clarify the
required software features to attach via Token-Ring LAN with IBM
Client Access/400 WSF (as we appear to the S/36 as the same product).
SETCOMM PROCEDURE
Line number .......................... 9
IBM Token-Ring Network adapter address
override .................... 400000000003
You may use the D C (display communication status) command and the
'3. Display system communications record' option to view the current
adapter address setting and speed (be sure to enter line 9 or 10).
First create a SNA Line member as follows:
1.0 SSP-ICF - CONFIGURATION MEMBER DEFINITION
1. Configuration member name ..................... PCLM
2. Library name .................................. SYNAPSE
3. Select one of the following:
Option (1. Create new member) ................ 1
2.0 SSP-ICF - CONFIGURATION MEMBER TYPE
Select one of the following options:
Option (3.SNA) ............................... 3
4.0 SNA CONFIGURATION MEMBER TYPE
1. SNA member type (SNA/IBM Token-Ring line mbr) .. 4
2. Will APPC or APPN be used? ..................... Y
12.0 SNA LINE MEMBER ATTRIBUES
6. Local system's station XID in hexadecimal ..... 2615A
(This is usually the last 5 characters of the system serial number)
7. Source service access point (SSAP) value ...... 04
12.5 REMOTE SYSTEM SELECTION
(This screen presents a list of the existing PC locations
configured, initially there will be none. You may use option
1 to create the new location entries. IMPORTANT - you must
create an entry for each location >directly< attached to the
S/36. If the PCs are attached via 802.2LLC then each PC must
have an location entry here. If you are connecting via Netware
SAA, then only the Netware server will have an entry here.
Be sure to use the roll keys here to scroll all entries into
view. When creating or or editing an entry:
13.0 REMOTE SYSTEM ATTRIBUTES
Remote system - I586CTR (your name will be here)
1. Remote system type (2-Peer) .................. 2
3. Remote system's block ID in hexadecimal ....... 050
(for NW SAA installs, use a block ID of 03E)
4. Remote system's station XID in hexadecimal .... 00000
13.5 REMOTE SYSTEM ATTRIBUTES
Remote system - I586CTR (your name will be here)
1. Remote adapter address ........................ 00C0B8000353
(for NW SAA installs, this is the NIC @ of the SAA server).
2. Destination service access point (DSAP) value . 04
(You will see screens 13.0 and 13.5 for each location created
from screen 12.5. Cmd7 back to main CNFIGICF screen when done
with all locations).
Next create a SNA subsystem member as follows:
1.0 SSP-ICF - CONFIGURATION MEMBER DEFINITION
1. Configuration member name ..................... S36APPN
2. Library name .................................. SYNAPSE
3. Select one of the following:
Option (1. Create new member) ................ 1
2.0 SSP-ICF - CONFIGURATION MEMBER TYPE
Select one of the following options:
Option (3.SNA) ............................... 3
4.0 SNA CONFIGURATION MEMBER TYPE
1. SNA member type (1. SNA subsystem member) ...... 1
21.0 SNA SUBSYSTEM MEMBER SELECTION
1. Select subsystem type (7. APPN) ................ 7
22.0 SUBSYSTEM MEMBER DEFINITION
1. Local location name ............................ S102615A
(This is the S/36 system name you must specify in the
router configuration !)
2. Network ID ..................................... APPN
28.0 APPN SUBSYSTEM MEMBER DEFINITION
1. Select one of the following .................... 5
5. Define session groups for multiple-session locations
(Option 5 is done once only.)
42.0 SESSION GROUP SELECTION
(This screen presents a list of the existing groups that are
defined - the AS/400 calls these entries MODES. You will
have existing entries for #BATCH, #BATCHSC, #INTER, #INTERSC
*BLANK. If one does not exist, create a group with option
1 called QPCSUPP ).
43.0 APPC AND APPN SESSION GROUP DEFINITION
Session group QPCSUPP
1. Session group type (1-Interactive) ............. 1
2. Maximum session limit .......................... 64
3. Number of locally controlled sessions .......... 00
4. Number of pre-established sessions ............. 00
44.0 APPC/APPN SESSION GROUP ADDITIONAL OPTIONS
Session group QPCSUPP
1. Receive pacing value ........................... 07
2. Maximum receive RU size ........................ 02048
3. Acquire remotely controlled sessions? .......... Y
(now you should return to screen 28.0)
28.0 APPN SUBSYSTEM MEMBER DEFINITION
1. Select one of the following .................... 1
1. Define locations in non-networking nodes
(you will be prompted after pressing enter for:)
2. Line member name (use name you specifed above).. PCLM
29.0 REMOTE LOCATION SELECTION
(This screen presents a list of the existing PC locations
configured. There will be a list of any previous entered
locations as well as new locations added in the line member
above (PCLM in our example).
You may use option 2 to edit existing entries that have the
'remote system' entered, but the 'location' entries are blank.
If needed (for example with NW SAA installs) you may use option
1 to create the new location entries. IMPORTANT - you must
create an entry for each PC that will be attaching to the S/36.
Be sure to use the roll keys here to scroll all entries into
view. An example of the lower half of the screen:)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OPTION LOCATION REMOTE SYSTEM
DBF NOVELL
JGF NOVELL
I586CTR I586CTR
JLL JLL
(Note here that I586CTR and JLL are stand-alone PCs that are
attached directly via 802.2LLC on the Token-Ring, hence the
'location' and 'remote system' name entries are the same.
However the DBF and JGF locations are connected via Netware SAA.
There could be many more entries connected via the SAA server
sharing the 'remote system' name of NOVELL, or many more
individual attached PCs similar to JLL. The entry specified in
the 'location' entry on these screens is the "PC location name"
for the PC router configuration!
When creating or or editing an entry:
30.0 REMOTE LOCATION DEFINITION
Remote system NOVELL Remote location DBF
2. Send alerts to this location? .................. N
41.0 APPC and APPN LOCATION DEFINITION
Remote system NOVELL Remote location DBF
1. Single-session locatoin? ....................... N
2. Stay operational? .............................. Y
(Again the entries on 30.0 and 41.0 are the same whether the
'remote system' and 'remote location' names are the same or
differ.)
SECEDIT COMM
Remote location name .............................. I586CTR
Location password ................................. *NULL
Require user password to start each procedure? .... N
Comments ............................. (whatever you want)
If prompted for a second screen, just take the defaults or change
them as you require. Use roll up and roll down to page through the
entries in the file.
ENABLE PROCEDURE
Subsystem configuration name ...................... S36APPN
Library name ...................................... SYNAPSE
Line number (use 9 or 10 for Token-Ring) .......... 9
Display parameters for subsystem .................. NOSHOW
Location name (optional, leave blank for all) .....
Line member name .................................. PCLM
Use the DISABLE procedure to stop APPC communications if required:
DISABLE PROCEDURE
Subsystem configuration name ...................... S36APPN
Location name (optional, leave blank for all) .....
Line number (use 9 or 10 for Token-Ring) .......... 9
If the S/36 APPC subsystem is not enabled or you are not connected to the S/36 properly you may get router errors such as:
1500-0003-00000004 or 4600-0014-00000000If you have not configured the SECEDIT COMM security options you will get:
0C00-0003--80F6051 Security problem.
In some situations, when starting all sessions on the PC at once (with the start all option) the S/36 can fail to properly start some sessions. This is very timing dependent on the S/36 end, and if it occurs, just retry the connection again for the failing session. If this is a problem for your installation, then start the sessions individually. If attempting to end a printer session and the session does not end, check to see if a document is trying to print. Some releases of the S/36 SSP do not automatically stop the print spool when the session is being ended and you must manually stop the writer or hold the documents before trying to end the printer session. When configuring default printers for a display session (see the display session advanced options), in order for the default printer to be properly configured, the printer session must be started BEFORE the display session is connected to the S/36. If the display is accidently connected first, just sign off, disconnect and reconnect, then sign-on again. Now check the default printer using the D (status) command and rolling down to the correct section. Printer subconsoles are only subconsoles while they are signed-on. When signed-off or disconnected, the system console will control the printer. Remember to sign-off the S/36 display sessions before ending them, otherwise unless you have auto-reply enabled on the S/36 the system console operator must answer an error message before you can connect the session again. Some releases of S/36 SSP have a problem sending report simultaneously to multiple printers at the same location (PC). If multiple printers are active on the PC at the same time, one printer may stop in the middle of the report without any error message (on the PC or S/36). Wait until the active printer is done, then stop and restart the failing printer spool writer. If the console receives error SYS-5835 Printer -- is offline ( 12 ) take option 1 to retry. These problems have only been seen with multiple printers on the same PC concurrently printing and reportably are the problems of the S/36 SSP.
Fraser's Hill and FHL are registered trademarks of Fraser's Hill Ltd. Other product and company names may be registered trademarks, trademarks, or service marks of their respective owners. FHL 14-Apr-2002 
|