SmartProduction Fixes (Last Modified: 2015/03/02)
back to support by product page

SmartProduction fixes are generally released as patches to be applied using the AMASPZAP utility. You will find a job stream to use as a wrapper around these patches in the SmartProduction INSTLIB in member MAINTJOB.

Left click on the fix link to view the patch. You can copy and paste the text into your job stream. Alternatively, right click on the fix link to save the text file on your PC. Later, you can transfer it to your host for application.

All users please note the following:

If you are planning to upgrade your z/OS System to V1R9 or higher, and if you are planning to run with CBLOC VIRTUAL31(IHAPCCA,IHALCCA) in an active DIAGxx member, then you must upgrade to SmartProduction V4.6.0 using the distribution files available on or after September 26, 2008. If this VSCR support is rolled back by IBM to earlier z/OS releases and you apply the maintenance to do so, then this SmartProduction upgrade will be required. If you run with CBLOC VIRTUAL24(IHAPCCA, IHALCCA) you do not need to upgrade to this distribution level.

There has been a report that the default REGION size of 3M is not sufficient in all environments when running reports. If this occurs, please update the members TMRSREP,TMRSSUM and TMRSTRND in the ISPFALL library. Change the REGION= parameters to a larger value.

All ACF2 users please note the following:

Starting with Version 4.4.0, three SmartProduction programs were converted to function as TSO Commands. In an ACF2 security environment with the Command Limiting Function active, these programs must be identified to ACF2. The three programs are TMRMDSAN, TMRMJBAN, and TMRMSTAT.

The following fixes are available for SmartProduction:

Version 5.3.0 Build 201401

RP299: DFSORT CPU and ZIIP times displayed may be inaccurate. (3/18/2014)

RP300: Report M3 may display job interval records in incorrect order. (3/18/2014)

RP301: Report M1 may ABEND with S0C4. (3/18/2014)

RP302: Panel M1 does not check CPU serial length. (3/18/2014)

RP303: Panel M2 does not check CPU serial length. (3/18/2014)

RP304: Report jobs may be submitted with invalid JCL. (3/18/2014)

RP305: Freeze Case J9A0. (3/18/2014)

RP306: Panels M1 and M2 may not accept a tape SMF input data set. (3/04/2015)

RP307: Report L9 may display a wrong pland name. (3/04/2015)

RP308: Report M1 CSV file may show info for same hour multiple times, or may abend with system 0C4. (3/18/2014)

Version 5.2.0 Build 201301

No fixes have been released.

Version 5.1.0 Build 201201

RP278: SUBMIT is not recognized as a valid command. (6/19/2012)

Version 4.8.0 Build 201008

RP239: Transfer date in global report L7, Panel J and Panel D may be incorrect. (10/4/2010)

RP240: The transfer rate in global report L7 might be incorrectly displayed. (9/7/2010)

RP241: GJC may abend with System 0CB. (9/28/2010)

RP242: GJC may abend with System 0C9. (10/4/2010)

RP243: Case J328 may be incorrectly issued. (10/10/2010)

RP244: Panel D incorrectly displays the details of a data set rename event. (10/10/2010)

RP245: Case D270 may be issued incorrectly. (11/1/2010)

RP246: Case D690 may be issued incorrectly. (11/1/2010)

RP247: Report D7may abend with system 0C4. (10/18/2010)

RP248: Extractor may set an invlaid Low/High SMF time range in the JOBHIST data base. (10/18/2010)

RP249: Report LA may not count HSM records correctly. (10/18/2010)

RP250: Extractor rejects SMF records belonging to a system whose name contains a $, % or @ sign. (11/1/2010)

RP251: GJC report may abend with system 0C4. (11/1/2010)

RP252: Panel J I/O counts may sometimes be incorrect for disk multi-volume sequential files. (01/27/2011)

RP254: Report J7 and Panel J may abend with 0C4. (11/2/2010)

RP257: J332 may be incorrectly issued, This fix affects DFSORT users, collecting DFSORT short SMF records. (01/27/2011)

RP265: J662 may be incorrectly issued.

RP268: Resource security check module bypassed if $ACCSYSIN= ALLOC is coded in the GLOBAL member. This file contains the instructions for applying the fix. This file contains JCL to help install the fix. This file contains the software fix (1 Link Library replacement). Download and save all three files to your PC.

TMRRCPU: The REXX to display the CPU information for the CEC/LPAR on which it is run has been updated. Please use this when you need to provide CPU change information to us for new license passwords. Copy this module to SMARTP.ISPFALL.

 

Version 4.7.0 Build 200908

RP227: ABEND S0C4 in Good Data Set Candidate Report.

RP228: The Extractor file dates may not be correct. In V4.7.0, the Extractor has been changed to record the actual date range contained in the Job History file, based on what was actually selected. This fix corrects the logic for that process.

RP229: Report GJC may wrongly terminate with RC 04.

 

Version 4.6.0 Build 200808

RP210: The Extractor might save a duplicate RMF 77 record.

RP215: The Extractor saves incorrect data set name from SMF FTP 119 record.

RP216: ABEND S0C4 in Good Data Set Candidate Report.

RP217: Panel D may ABEND with S0C9.

RP220: CLIST SMARTPC may identify migrated data sets as tape data sets.

RP227: ABEND S0C4 in Good Data Set Candidate Report.

 

Version 4.5.0 Build 200801

RP199: GJC and GDC may end with TMR010E ERRID=01.

RP203: The GJC report may abend with S0C9.

RP207: The Extractor may abend with S0C7.

For fixes to earlier releases, please contact Technical Support.

home | products | about Axios | support | contact us