|
|
 |
PHOENIX/PREFERENCE VTAM Interface Trouble
Shooting Procedure
PHOENIX/PREFERENCE has a built in VTAM diagnostic
tool that will report information when a VTAM error condition
occurs. To turn this facility on you can either add the parameter
"WTO=YES" to the PHOENIX/PREFERENCE startup parameters (see the
PHOENIX/PREFERENCE System Guide) or a supervisor can issue the
command "WTO=YES" from the PHOENIX/PREFERENCE supervisor type
command line (see the PHOENIX/PREFERENCE Supervisor Guide).
Having the GC306 messages that are generated
when a VTAM error occurs are extremely helpful in diagnosing the
cause of the error (these messages will be written to the JES Log).
Additional messages are generated due to "WTO=YES" as follows:
- GC325 LOGOFF – issued when an LU signs off
of PHOENIX/PREFERENCE
- GC326 LOGON – issued when an LU signs on
to PHOENIX/PREFERENCE
When PHOENIX/PREFERENCE forces an LU off
(CLSDST's the LU due to an unrecoverable VTAM error condition),
a GC315 error message is written to the JES Log. The GC315 message
would appear regardless of whether the "WTO=YES" option is turned
on. To aid in diagnosing a PHOENIX/PREFERENCE
VTAM error we recommend the following procedure:
- Add the parameter "WTO=YES" to the startup
operating parameter for PHOENIX/PREFERENCE. That way this diagnostic
tool will already be active when a VTAM error occurs.
- When the VTAM error does occur again, please
send to Pathlore the JES LOG containing the diagnostic GC306,
etc. error messages.
- At the time the error occurs (is detected)
it would be good to have a supervisor signon and determine if
the problem LU is still connected to PHOENIX/PREFERENCE. This
can be accomplished by using the Line Status supervisor command
("ls").
- If the terminal appears to be hung
and still has a session with PHOENIX/PREFERENCE, please issue
the "Line Dump" and "Line Off" commands for the session line
number. This should force the session off and clear up the problem.
This is accomplished by performing the following:
- Observing the session line # associated
with the problem termID from the Line Status command.
- Issue the Line Dump command for that
number as "line dump/#".
- Issue the Line Off command as "line off/#".
- Send the Diagnostic Dump to Pathlore
along with the JES LOG as stated above.
- If the terminal appears to be hung (the LU
may be in a pending state) and no longer has a session with
PHOENIX/PREFERENCE, then we recommend recycling PHOENIX/PREFERENCE.
If after the recycle the LU's pending state remains unchanged,
then the terminal was no longer in session with PHOENIX/PREFERENCE.
I recommend looking to another layer that may be involved such
as a VTAM session manager.
|
|
|
Order
Your Upgrade Today!