If you do not invoke IPCS from TSO READY, before invoking PDF, and
then invoke IPCS, and you have a tasklib (Via STEPLIB, TSOLIB, ISPLLIB,
etc),
you may see a horrendous performance problem when you hit PF3 to terminate
an
IPCS report. There is recently opened APAR will will address this
problem.
Apar: OA38921
Abstract: ONCE AN IPCS REPORTS BEGINS, IT CAN TAKE MINUTES BEFORE
CONTROL IS RETURNED TO THE USER
ERROR DESCRIPTION:
It can take minutes for PF3 to end a large IPCS report when the
following are conditions are true:
1. You are in split screen IPCS mode, and more than 1 screen
session is in an IPCS report (so this PF3 is not terminating
the last report.
2. IPCS was not invoked before PDF, so IPCS is using the
TSO/E IKJURPS interface to manage IPCS functions which
are common between the sessions.
You can bypass this problem by going back to TSO READY,
entering IPCS NOPARM , and then PDF.
Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
