home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 8
/
CDASC08.ISO
/
VRAC
/
CMINFO.ZIP
/
II06554.CM
< prev
next >
Wrap
Text File
|
1993-04-27
|
20KB
|
243 lines
PRINT SELECTION FOR APAR - II06554 93/04/27
PIN INFO-PC-LIB-100 II06554-IN-INCORROUT
F - - -
DEBUGGING TIPS FOR VSE FILE TRANSFER AND ANY PC 3270 EMULATOR
OS2 COMMUNCATION MANAGER PERSONAL COMMUNICATIONS 3270 PERCOM
END OF ABSTRACT FESN5NFO000-000
REPORTED RELEASE R001
ERROR DESCRIPTION:
DEBUGGING TIPS FOR FILE TRANSFER TO A VSE HOST FROM ANY
IBM OR OEM 3270 EMULATOR FOR THE PC INCLUDING:
PERSONAL COMMUNICATIONS 3270 (PERCOM)
PC3270 EMULATION PROGRAM, ENTRY LEVEL
OS2 COMMUNICATIONS MANAGER
HCON RS6000
1) What release of VSE are you running?
If the customer is not sure tell them to use
LIBRARIAN to list SPLEVEL.PROC in IJSYSRS.SYSLIB
This is a list of the current releases:
566634500 B72 VSE/SP Unique 3.1.X, 3.2.2, 3.2.3
568600600 C72 VSE/SP Unique 4.1.1, 4.1.2, 4.1.4
568602801 F10 VSE/SP Unique VSE ESA 1.1.X, 1.2.2, 1.2.3
VSE file transfer is not called IND$FILE. It is shipped
with the above package component id and it consists of
a phase called INWPCCOM. Some customers refer to the VSE
file transfer function as IWS (Intelligent Workstation
Support), or IUI file transfer. They may also refer to it
as CICS file transfer, but if they are running VSE then
they are using INWPCCOM and VSE supplied transactions
IND$ or INW7. Both of these transactions will invoke
INWPCCOM.
2) What messages are received on the PC side?
3) What messages are received on the Host side?
4) Is the VSE release the most current one available?
The most current VSE releases are 3.2.3, 4.1.4, ESA 1.2.3.
Even if the release is current there may be some outstanding
apars. Search on the symtoms in the PA library for VSE
apars. For more messages or symptoms ask the customer to
recreate the error and then display the bottom of the
INSPECT MESSAGE LOG DIALOG.
If any VSE apars are required PLEASE have someone from the
VSE level2 group order the apar as there are special
ordering procedures.
5) Do both the SEND and RECEIVE fail?
6) What is the exact SEND or RECEIVE command that was entered
including any options.
For example:
SEND PC.FIL FILENAME (FILE=HTF ASCII CRLF REPLACE
RECEIVE PC.FIL (FILE=LST KEEP
7) Where is the send or receive directed to or from?
File transfer can be performed to or from:
VSE Host Transfer File (HTF)
This file is a large VSAM file that contains seperate
entries for each file that a user sends to it. The entries
are connected to a directory within the HTF for that
user. VSE provides dialogs to move the files from this
large HTF to other VSAM files or ICCF members.
CICS Temporary Storage
A CICS appication can then manipulate the TS queue.
VSE/POWER queues
A file can be sent or received from the POWER LIST
queue (output from HOST jobs).
A file containing a VSE job can be sent to the POWER
RDR queue.
A file can be received from the POWER PUNCH queue.
8) How is the PC attached to the HOST?
9) If attached through a 3174, hardware configuration question
125 bit 6, File Transfer aid must be set on.
The 9370 Workstation adaptors also have a file transfer aid
bit and this will not be turned on if all defaults are taken.
If this bit is not on the VTAM buffer trace will show empty
buffers and a TRANS10 will be issued at the PC.
Customers may need assistance from their CE to set this bit
on.
10)Is EXTDS defined in the CICS terminal definition? If it is
not on, this can cause the file transfer to hang and a
TRANS10 will be issued by the emulator on the PC side.
11)Examine a trace, either VTAM BUFFER, SIO/IO, or the
trace provided by the emulator and make sure that
the emulator is following proper protocol for the
mode that the PC is configured in (CUT or DFT).
12)Here is a list of VSE apars that may be applicable
depending on the symptoms. Please have someone from
VSE level2 order the apars if necessary as there are
special ordering procedures:
V3.X.X V4.X.X V1.X.X SYMPTOM EMULATOR
------ ------ ------ ------- --------
PN22379 NONE PN10293 STORAGE VIOLATION/AEIV OS/2 COMM.MAN.
PN14880
PN13042 PN12904 PN09743 COMFTR08 (try NOCLEAR) PERCOM 3270
PN09132 PN01653 PN05134 TRANS10 ANY IBM/OEM
II02492 II02492 II02492 SETUP PROBLEMS ANY IBM/OEM
13)DOCUMENTATION NEEDED TO PURSUE FAILURES:
===============================================================
One of the following traces will be required to determine if
the error is being caused by the VSE software of the emulator.
For abends in VSE code a CICS AUX trace may also be required.
IWS TRACE:
---------
This is available as an option on the SEND/RECEIVE command
after VSE/SP 3.2.0. It is documented in the VSE Guide For
Solving Problems.
VTAM BUFFER TRACE:
-----------------
The VTAM buffer trace can be started and stopped by entering
the following commands at the VSE system console:
'F NET,TRACE,TYPE=BUF,ID=TERMID'
'F NET,NOTRACE,TYPE=BUF,ID=TERMID'
For TERMID use the entire VTAM NETNAME. Use TPRINT to print
the trace. The following messages will be issued:
IST907A - SNAPSHOT MODE TPRINT ENTER Y OR N
Reply 'NO' to this message.
IST905A - ENTER TRACE PRINT OPTIONS OR 'CANCEL'
Reply 'PRINT BUF=ALL'
SDAIDS SIO/IO TRACE WITH CCWD:
-----------------------------
This job will set up the SDAIDS trace:
// JOB SDAID
// EXEC SDAID
OUTDEV T=tcuu
TRACE SIO AR=Fn UN=cuu OUTP=(TOD CCWD=2000)
TRACE IO AR=Fn UN=cuu OUTP=(TOD CCWD=2000)
/*
/&
Fn is the CICS/ICCF partition. tcuu=tape device for trace out
UN=cuu is the line, terminal, or controller being traced.
If controller is being traced be sure to reduce the traffic.
Submit the above job. Enter STRTSD. Recreate the error.
Enter STOPSD then ENDSD. Use DOSVSDMP to print the trace.
============================================================
COMMON USER ERRORS, CONFIGURATION ERRORS, OR EMULATOR PROBLEMS
=============================================================
A) MSGINW0002I from a module name ending with '0' and
customer indicates the PC is connected in DFT Mode.
This is a generation and tailoring error, the module
names ending in '0' are used in CUT (Control Unit Terminal)
Mode. The customer needs to make certain that the PC,
controller, VTAM tables, and the CICS terminal entries are
configured for EXTENDED DATA STREAMING when using the PC as
a DFT (Distributed Function Terminal).
B) MSGINW0002I with RC=0001 and the error description for
the affected module is 'INVALID REPLY (NO AID ENTER)'.
This means the response buffer did not begin with X'7D'
(7D is the 3270 AID byte for an Enter Key).
This message will also be issued if the user tries to
toggle back to the host or if they use Ctrl-Break to break a
hang before file transfer is complete. The Ctrl-Break will
send in data that will not begin with x'7D'. The reason for
the hang should be investigated.
C) FILE TRANSFER AID BIT PROBLEMS: MSGINW0002I TRANS10 HANGS
MSGINW0002I TRANS10 hangs can occur if the 3174 Control Unit
Hardware configuration Question #125 bit 6, 'FILE TRANSFER
AID', is not set on. Without this bit turned on a RECEIVE
will work but SEND will fail. A VTAM Buffer Trace will show
empty data buffers.
9370 Work Station Adaptors can have the same problem if
all defaults are taken.
Hardware configuration Question #125 also applies to
D/T9221. See 'Planning For Your Workstation Subsystem.'
MSGINW002I TRANS10 HANG
This particular customer was running VSE/SP 4.1.x, EE
(Entry Emulator) 1.1,1.2,2.0 on a PS/2 and attached through
a 3299 multiplexer which also contains a 6120 or 6020 WSA.
This could probably happen with any version of VSE and hangs
could occur with any emulator but with EE the RECEIVES would
work but sends fail. The file was actually transferred on
the SEND but the session would hang at the end and multiple
TRANS10's were issued. This problem is described in APAR
IR87131. The FILE TRANSFER AID BIT needs to be set in the
Work Station Adaptor. See PLANNING FOR YOUR WORKSTATION
SUBSYSTEM GA24-4223 p.2-9. This customer's CE also found
that the WORKSTATION CONTROLLER FEATURE 6120 card in the
9370 expansion cage in the 9221 system was not properly
configured to operate with 3270 emulation. It must be
set to communicate with a 3174 not a 3274.
D) 3274 CONTROL UNIT - Customer was experiencing a file transfer
hang at the same exact byte count every time. The problem
was intermittent and occurred mostly with larger files.
SOLUTION: Hardware Configuration Question #164 PS TERMINAL
BIT must be turned off to work correctly.
E) HANG WAIT or HUNG condition on PS/2 using 4300 ICA and
the 3270 Emulation Version 3 Control Program caused by
not having EXTDS, Extended Data Streaming in the TCT and
VTAM was not configured for DFT Mode.
F) FTTERM CONFIGURATION PROBLEMS:
MSGTRANS10 TIMEOUT on PC running FTTERM with a D/T3174 AEA.
If the 3174 AEA ports are configured as either
FC (FTERM COLOR) or FM (FTTERM MONO)
then answer '1' to 'USE SPECIFIC KEYBOARD MAP (1=YES 0=NO)
prompt on the FTTERM configuration. See the 3174 Terminal
User's Reference. There was not IND$FILE coming in from
the emulator on the PC.
G) ABENDAICA AICA USER EXIT ROUTINE.
If a user tries to expand a record in their user exit
routine they have to do a GETMAIN and more the record
before they expand it. See SP/Administration Manual
SC33-6306-00, Page 248, Your Exit Routine Should Perform
The Following Steps: STEP 4.
H) When RECEIVE is used from PS/2 TRANS10 TIMEOUT
0 BYTES RECEIVED and when you Hotkey back to the host
and hit Enter Key, MSGINW0002I INWPRCVE RC1 is
issued. The TRANS10 was due to not having EXTDS coded.
The INW0002I INWPRCVE RC1 was due to Hotkeying back to the
and hitting the Enter Key. The problem is resolved by
coding EXTDS in the TCT.
I) HANG OR MSGINW0002I INWPGET1 RC=0002 when using PERCOM
Personal Communications 3270 V2 under Windows. The
customer signed on to the IUI and used PF6 to get into
native CICS. They opened a window and sent a file to the
host. They received MSGINW0001I File Transfer Complete at
the PC but it did not show up on the host screen as it does
in DOS Mode. They hit enter or PF3 on the host session and
INW0002I INWPGET1 RC=0002 was issued. The RC2 means that no
acknowledgement was received from the PC. The trace showed
normal DFT protocol flow up until the host sent out the
Insert Request + Data (msg) and then the PC never responded
with an Insert Data acknowledgement positive. The customer
found that by increasing the TIMEOUT option from 30 to 60
on the windows panel the INW0001I would appear at the host
ADDITIONAL KEYWORDS AND COMPONENT IDS:
MSGINW0002I INW00002I TRANSMISSION ERROR HOST IS NOT RESPONDING
PERCOM V2 DOS 562123900 V3 DOS 562142601 cminfo OS2 ES1
PERCOM V2 WINDOWS 562123901 V3 WINDOWS 562142602
COMMENTS:
Closing to retain in the database.
93/03/08,ENDICOTT