FYI - SF64187 for V4R5M0
APAR Identifier ...... SA68939 Last Changed..00/10/27
OSP-INCORROUT DISPLAY OPEN FILES MUST USE F10 TO SEE I/O
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 97/10/30
Component .......... 5769SS100 Duplicate of ........
Reported Release ......... 410 Fixed Release ............ 999
Component Name 5769 BASE V4 Special Notice
Current Target Date .. Flags
SCP ................... OS/400
Platform ............ OS/400
Status Detail: SHIPMENT - Packaged solution is available for
PE PTF List:
Release 410 : SF44659 available 97/11/03 (1000 )
Release 420 : SF48724 available 98/05/15 (9068 )
Release 430 : SF53110 available 99/01/15 (1000 )
Release 440 : SF57483 available 99/07/01 (1000 )
Release 450 : SF64187 available 00/10/27 (1000 )
Parent APAR: SA46331
Child APAR list:
THIS APAR WAS SYSROUTED FROM R360 SA46331.
THIS APAR WAS SYSROUTED FROM R305 SA37000.
THIS APAR WAS SYSROUTED FROM R230 SA35851.
See problem summary.
Key words: dspjob f10 qdmdspof
When displaying a job (dspjob), starting with v2r3, and choosing
the option to display open files, the user is presented a panel
showing activation groups, from which he must press cmdkey10 in
v2r3 or cmdkey11 in v3r0m5, v3r1, or v3r6 to see the I/O
details. The panels are presented in this order to accommodate
activation groups since the same file, library, and member may
be opened for more than one activation group. The initial
display doesn't have enough room to accommodate all of this
information. However, this design is inconvenient for the user
and is also inconsistent with the order presented by the
display call stack option.
In V2R3 the ILE programming model introduced Activation
Groups to the AS/400. With these new Activation Groups,
came the concept of scoping a file open to one of them.
In a related change, we also added the concept of scoping
a file open to the Job level. Since there now existed
the possibility of the same File, Library and Member being
opened in more than one Activation Group, it was necessary
that we return the Scope and Activation Group of each open
in order to distinguish between these open occurrences.
The I/O data which used to be displayed on the initial
screen had to be moved to a subsequent screen to make room
for the Scope and Activation Group fields. Since the new
fields were required by the customer to identify the
particular record of the displayed output that he or she was
interested in, it was more appropriate to display
this information on the initial panel.
The unfortunate, yet unavoidable, space limitations
on the initial screen forced us to make a choice.
Considering the importance of the new scoping data as selection
criteria, we chose to put the new fields on the initial screen.
We realize that not all customers use the ILE environment.
for those who do not, and prefer the I/O details to be
displayed first, we have created this request only PTF.
By applying this PTF all users on the system will
have the I/O details appear first when they use the
display open files option off the WRKJOB or DSPJOB
screen. This will happen even if users are running
in the ILE environment.
A re-install of the operating system may be necessary,
if this PTF is permanently applied and users need the
screens to appear in the correct order.
Since the majority of customers use the ILE environment,
this PTF would cause problems for them. This PTF will
NEVER be placed in a CUM package.
Request only PTFs will be created. A customizable
feature may be created in a future release.
Below are 3 different ways of viewing the I/O details when
Displaying Open Files.
I/O details are displayed on a second screen. Press F10 (V2R3)
or F11 (V3R0M5 or V3R1) to see them.
WRKJOB OPTION(*OPNF) OUTPUT(*PRINT)
DSPSPLF FILE(QPDSPJOB) SPLNBR(*LAST)
DSPJOB OPTION(*OPNF) OUTPUT(*PRINT)
DSPSPLF FILE(QPDSPJOB) SPLNBR(*LAST)
MESSAGE TO SUBMITTER: UPDATED 10/25/00