Upgrade OS390R7, Subset SDSF:
This subset contains installation information for SDSF
for OS/390 Version 2, Release 6, Modification 0.
Change Summary
DATE LAST
CHANGED SECTION
1. 99/03/01 INSTALLATION INFORMATION
2. 01/10/11 DOCUMENTATION CHANGES
3. 00/04/11 GENERAL INFORMATION
4. 02/08/09 SERVICE RECOMMENDATIONS
5. 99/03/01 CROSS PRODUCT DEPENDENCIES
DATE APAR PTF VOLID COMMENTS
5 02/08/09 PQ62907 UQ68579 0208 HIPER POTENTIAL OVERLAYS WHILE
4 99/10/08 PQ19317 UQ21821 9809 HIPER SDSF LOOP OCCURS IN ISFDSP
3 99/08/31 PQ18576 UQ22362 9810 HIPER SDSF SUPPORT FOR
2 99/08/31 PQ23563 UQ29096 9904 HIPER SDSF SUPPORT FOR
1 99/06/07 PQ26310 UQ30277 9906 HIPER ABENDS09C7 OCCURS WHILE
This section contains changes to the product's Program Directory.
10. 99/03/01 To access SDSF directly from the ISPF primary option menu,
the ISPF panel ISR@PRIM (or other primary option menu
panel) may need to be updated. This includes adding text
for the SDSF option and defining panel logic to invoke
SDSF. SDSF provides sample panel ISF@PRI4 in data set
SISFPLIB which can be used as a model for the changes.
9. 99/03/01 Installations with OS/390 must update the SYSLIB entry used
for SDSF assemblies to use SHASMAC, the new ddname for the
JES2 macro data set.
8. 99/03/01 When using the ISFACP utility to convert ISFPARMS Assembler
macros to dynamic ISFPARMS statements, the output data set
to contain the dynamic ISFPARMS statements must be
pre-allocated.
7. 99/03/01 HLASM message ASMA437N and SMP message GIM24001E may be
issued for the following modules because they contain
assembler *PROCESS statement USING(WARN(0)): ISFDFGT,
ISFDMFUV, ISFDSP, ISFPRINT, ISFSUBS and ISFSVC. The
messages and the resulting return code 02 may be ignored.
6. 99/03/01 When assembling SDSF with the High-Level Assembler (HLASM),
use option USING(WARN(2)).
5. 99/03/01 Installations executing SDSF from LPA must add command
'SDSF' to the ISPF TSO command table, ISPTCM, if message
'IKJ56500I COMMAND SDSF NOT FOUND' is received when SDSF
is invoked with command 'TSO SDSF' from ISPF. Module
ISPTCM should be updated with the following ISPMTCM macro
coding: 'ISPMTCM FLAG=02,ENTNAME=SDSF'.
4. 99/03/01 Sample installation jobs ISFINLPA, ISFCOPY and ISFLINK are
no longer shipped in the AISFJCL data set. In order to
execute SDSF from the LPA, add the SISFLOAD data set to
the LPALSTxx member in SYS1.PARMLIB.
3. 99/03/01 In order to use the sysplex-wide DA function in a sysplex
that has both an RMF 5.1.0 system (or systems) and an RMF
5.2.0 or higher system (or systems), the SISFLOAD data set
must be made accessible to the RMF 5.1.0 started task, even
though no data is gathered from the RMF 5.1.0 system.
2. 99/03/01 Some SDSF target and distribution library data set names
have changed. As of SDSF 1.5.0, SDSF now conforms to the
IBM product packaging rules for data set names. As a
result of these changes, SDSF will use its own target
library, SISFSRC, instead of the SMPSTS and SMPMTS data
sets. Refer to the Program Directory for a listing of
current data set names.
1. 99/03/01 An ABEND16D may be received during initialization if the
SDSF SVC (module ISFSVC linked as IGX00011 in SISFLPA) is
not installed in the LPA. The SISFLPA data set must reside
in the LPA.
This section outlines major errors in the product's published
documentation.
2. 01/10/11 We have recently seen an increasing number of situations
where the spool data is somehow being corrupted. SDSF is
not responsible for creating or maintaining this data, it
is merely a user of the data. To provide some relief to our
users, we are implementing a change to the LOG function to
not ABEND on some of these intermittent spool errors. With
this new change, whenever SDSF recognizes that there is
corrupt data on the spool, it will return the user to the
"SDSF Primary Option Menu" and display the message "SPOOL
DATA ERROR" next to the title. At the same time, the LOG
function will be disabled since the data is corrupt and
there is nothing SDSF can do to recover the data.
Subsequent attempts to enter the LOG display will result in
the message "LOG FUNCTION INOPERATIVE". At this point, the
user has the option of displaying the log data using either
SDSF Browse or ISPF Browse. The LOG function is locked
until the user exits and restarts SDSF.
1. 99/07/22 Browsing output datasets using the SDSF browse action
character (S), displays the dataset starting from column
two. Scroll left to display column one.
This section contains general information, i.e. SYSGEN hints/tips.
20. 00/04/11 When operating in 27x132 screen mode, the current SDSF
design does not contain room for an attribute byte which
would allow the user to select where to place the command
line. This has the effect of the command line always being
at the top when in 27x132 mode and the user cannot move it
to the bottom. This is a permanent restriction of the
present SDSF design.
19. 99/03/01 A workstation interface for SDSF, (E)JES/2 (TM), is
available from Phoenix Software International. See the
Phoenix Software International website for more information
(http://www.phnxsoftware.com).
The following OS/390 R5 SDSF maintenance is
recommended when using the workstation interface:
APAR PQ12500 PTF UQ15989 AFD Log stamp error
18. 99/03/01 Upon displaying the Operlog panel, users hold a connection
to the Operlog log stream (MVS Logger component). The
connection is held even as other SDSF panels are displayed
and is not disconnected until the SDSF session is ended.
While SDSF users are connected to the Operlog log stream,
the Operlog structure cannot be altered.
17. 99/03/01 Under SDSF R600, when using ARRANGE command to arrange the
fields on the various displays to suit individual
preferences, if you try to use the profile under SDSF R500
system, the SORT settings are eliminated and the ARRANGE
settings are reset to the default. Using the SORT command
for migration for SDSF R500, and R600 and higher, the SORT
command is ignored from ISFPROFS due to a design change.
The SORT command migration for SDSF R600 and higher, will
be migrated. No error message is issued. When using the
ARRANGE command, with different releases of SDSF, if new
fields are introduced that were not present at previous
SDSF releases, the 'ARR CRITERIA OBSOLETE' message will be
displayed. Using ISFPARMS, or SERVER PARMS, customization,
you can duplicate the older fields, used at the lower level
of SDSF, to be the same at the higher levels of SDSF. But
this would eliminate the new fields that are introduced
with the newer level of SDSF.
16. 99/03/01 SDSF omits the server name from the SAF resource check
for group membership in ISFPARMS (SAF resource
GROUP.group-name.server-name in the SDSF class) when the
SDSF server address space is not active. When the server
address space is not active, SDSF checks authorization to
resource 'GROUP.group-name.'. Installations intending on
using SAF to control group membership in ISFPARMS, without
the server address space being active, will need to define
a generic resource profile such as GROUP.group-name.* for
proper authorization (a default server-name of 'SDSF'
should not used when defining the resource profile).
15. 99/03/01 SDSF DEST command processing internally uses name 'Unnnn'
for local printers defined in JES2 with PRT(nnnn)
initialization statements. For example, SDSF will
internally reference PRT(100), using the same number, as
as 'U100'. Installations that have JES2 PRT(nnnn)
statements that are not mapped by a JES2 DEStid statement
to a DEST of Unnnn, using the same number, may receive
unexpected results from the SDSF DEST command. For
example, PRT(100) should be mapped by DEStid to a DEST of
U100.
14. 99/03/01 When ULOG is active and issuing commands that return many
individual responses, such as a JES2 $DI command, all
responses may not be shown / overlayed on the panel being
viewed. Users may also find the number of responses for
the same command may differ from command to command. All
responses, however, will appear in the User Session Log
(ULOG panel). Command parameter L=Z (i.e. $DI,L=Z) can be
used to convert individual responses to one multi-line
response, allowing the entire response to be shown on the
panel being viewed, up to one screen of text.
13. 99/03/01 In order to use the SERVER parameter on the SDSF
initialization command (i.e. 'S.SERVER(server-name)'),
users must have READ authority to SAF resource
ISFCMD.OPT.SERVER in the SDSF class. Without authority to
the resource, SDSF will issue message 'INVALID COMMAND'
after initialization is complete.
12. 99/03/01 Installations may experience performance degradation when
using the Operlog panel. The design of the Operlog
processing routines is currently being reevaluated in an
effort to improve overall performance. Customer
requirement REQ00059224, titled 'Improve performance of
SDSF with OPERLOG', is on record and has been RECOGNIZED
as a development objective. The requirement covers all
Operlog functions, including scrolling, finding and
filtering. Suggestion (SUG) APAR PQ07414 also describes
the performance problem and suggests operational techniques
as possible circumventions.
11. 99/03/01 Installations using sample exit usermod ISFUM01 (previously
known as UM00001) should use field DSJSCLAS for job output
class verification. Usermods from previous SDSF releases
(SDSF 1.4.0 and prior with SDSF APAR PN65878) may have been
coded using field DSJSPDBC.
10. 99/03/01 SDSF cannot display its panels in windows created by a
previous ISPF dialog. The SUSPEND option should be used
with the ISPF SELECT service when SDSF is invoked through
an EXEC.
9. 99/03/01 When ULOG is active and issuing MVS command '/D R,L', some
responses may not be shown. By default, the display
outstanding operator requests command shows only those
messages appearing on the console from which the command
was issued. Command '/D R,L,CN=(ALL)' will show all
outstanding replies.
8. 99/03/01 When activating an extended console, SDSF ignores any RACF
OPERPARM defined for the console. To use the RACF
OPERPARM, set flag UPRS2SOP in byte UPRSFLG2 to a B'1' in
the Initialization Exit Point in module ISFUSER.
Alternatively, the OPERPARM can be supplied to SDSF by
placing its address in field UPROPERP. Note that the MIG
parameter of the SDSF 'SET CONSOLE' command is ignored when
either UPRS2SOP or UPROPERP are set.
7. 99/03/01 The Display Active Users panel may show an incorrect EXCP
count in the EXCP-CNT field when a job has been assigned to
an initiator, but has not yet started executing (waiting
for data sets, etc.). The EXCP count shown is taken from
the ASCB and represents the EXCP count of the previous job
step.
6. 99/03/01 As of SDSF 1.3.3, the Display Active Users panel exploits
the RMF Application Interface (provided as RMF SPE APAR
OY49185). If the RMF API is installed and accessible, SDSF
will default to getting data about jobs and system
utilization using the RMF API. Installations with a
modified ISFDA module may find that the changes are not
being driven. Support is provided in the Initialization
Exit Point in module ISFUSER to bypass the use of the RMF
API (set flag UPRNORMF in byte UPRSFLAG to B'1'). Refer to
the SDSF Customization and Security manual for additional
information.
5. 99/03/01 If a semi-colon (;) is specified as the MVS command
delimiter, users will not be able to stack multiple JES2
commands on the command line without preceding each command
with a JES2 command identifier (i.e. $). This will also
cause the $M command generated by SDSF to fail. Refer to
the MVS Initialization and Tuning Manual, CONSOLxx member
for additional information.
4. 99/03/01 SDSF should be reassembled whenever JES2 maintenance is
applied to ensure that proper offsets are used when
accessing control block information. Sample UCLIN jobs
(members ISFUCnnn in the AISFJCL data set) are provided to
cause SMP/E to perform automatic reassemblies when control
blocks have been updated by maintenance.
To perform reassemblies as needed, sample job ISFASMP
is provided and recommended to perform reassemblies through
SMP/E. If reassembling using sample job ISFASSEM, be sure
any maintenance that affects modules in the AISFLOAD data
set is SMP/E accepted prior to running the job as ISFASSEM
link edits modules using input from the AISFLOAD data set.
Installations using SYS1.MODGEN and running ISFASSEM will
need to add the data set name to the job's SYSLIB
concatenation. SYS1.MODGEN should be added immediately
before SYS1.AMODGEN.
3. 99/03/01 Users may receive an ABEND106 during SDSF initialization
if either the SISFLOAD or SISFLPA data sets has gone into
extents. Compress and re-access the data sets.
2. 99/03/01 Users may receive message ISF030E SDSF TERMINATING DUE TO
PROGRAM AUTHORIZATION FAILURE, REASON=08 during SDSF
initialization for one of the following reasons.
1) SDSF is executing out of a load module that is not APF
authorized. SDSF must run APF authorized.
2) An unauthorized library is concatenated with the SDSF
load module in a STEPLIB procedure. All libraries in
the STEPLIB concatenation must be APF authorized.
Otherwise, the entire STEPLIB procedure is treated as
unauthorized.
3) One or more SDSF modules are executing out of the
ISPLLIB concatenation. SDSF modules should not be
located in the ISPLLIB concatenation since ISPLLIB is
generally set up to run unauthorized.
1. 99/03/01 Users may receive an ABENDU0081 during SDSF initialization
for one of the following reasons. Use the module name,
module assembly level, and system JES2 level information
received in the ISF020E SDSF LEVEL ERROR message for
problem diagnosis.
1) If the ISF020E message has a good module name and
system JES2 level (both readable and/or expected), but
a bad module assembly level (unreadable and/or
unexpected), the problem is the result of SDSF not
being correctly assembled against the JES2 level that
is currently executing on the system.
2) The module name returned in the ISF020E message may not
be APF authorized.
5 02/08/09 PROBLEM: (PQ62907) POTENTIAL OVERLAYS WHILE USING SDSF
TRACE FACILITY
USERS AFFECTED: All SDSF 1.9.0, OS/390 R5 SDSF, and
higher users.
RECOMMENDATION: INSTALL UQ68579 ON VOLID 0208 (HQX1900)
4 99/10/08 PROBLEM: (PQ19317) SDSF LOOP OCCURS IN ISFDSP USING
VARIABLE FLDS IN DA
USERS AFFECTED: All OS/390 R3 SDSF, OS/390 R4 SDSF
and OS/390 R5 SDSF users.
RECOMMENDATION: INSTALL UQ21821 ON VOLID 9809 (HQX1900)
3 99/08/31 PROBLEM: (PQ18576) SDSF SUPPORT FOR COMPATIBILITY WITH
OS/390 V2R7 JES2.
USERS AFFECTED: All OS/390 R7 SDSF users.
RECOMMENDATION: INSTALL UQ22362 ON VOLID 9810 (HQX1900)
2 99/08/31 PROBLEM: (PQ23563) SDSF SUPPORT FOR COMPATIBILITY WITH
OS/390 V2R8 JES2.
USERS AFFECTED: All OS/390 R8 SDSF users.
RECOMMENDATION: INSTALL UQ29096 ON VOLID 9904 (HQX1900)
1 99/06/07 PROBLEM: (PQ26310) ABENDS09C7 OCCURS WHILE ISSUING MVS,
JES2 AND CHANGING WLM MODES AFTER INSTALL OF SDSF
PTF UQ26963.
USERS AFFECTED: All SDSF users with APAR PQ23530 applied.
RECOMMENDATION: INSTALL UQ30277 ON VOLID 9906 (HQX1900)
This section contains information that is dependent upon another
product other than this subset ID. It also contains information
dealing with migration and product coexistance.
1. 99/03/01 INTERDEPENDENT PRODUCT: JES2 5.2.0, OS/390 R1 JES2 and
OS/390 R3 JES2
PROBLEM: Sysplex-wide DA panel issues message 'JCT NOT
AVAILABLE' when any address space is selected for
browsing.
USERS AFFECTED: All JES2 5.2.0, OS/390 R1 JES2 and OS/390
R3 JES2 users without JES2 APAR OW24261
applied.
RECOMMENDATION: INSTALL UW34685 ON VOLID 9612 (HJE5520)
INSTALL UW34686 ON VOLID 9612 (HJE6601)
INSTALL UW34687 ON VOLID 9612 (HJE6603)
PTF Include List
PTF Exclude List
PE APAR List
End of Upgrade OS390R7
, Subset SDSF
, as of 2016/11/30.
|