IBM Power Systems

IBM Power Systems

About This Blog

Warm wishes and welcome to all AS400 Administrators and Operators.



This is exclusive blog for iSeries system Administrators working anywhere in the world. Also a place for guys and gals who want to share knowledge pertaining to iSeries. This blog has been designed for exchanging knowledge on AS400 or iSeries server administration and operations.



Friday, March 12, 2010

Locating PTFs Downloaded by SNDPTFORD Command

The DSPJOBLOG command can be used, in this case, to find the SNDPTFORD SF98540 e.g. command last used. The joblog was reviewed to find a message (assuming the SNDPTFORD xxxxxxx command was successful) as follows:


Cover letter has been copied to file QAPZCOVER member QSF98540.
Placing your cursor on the above message in the joblog and pressing F1 will yield the following message description:

Message ID . . . . . . : CPI35F1

 
Message . . . . : Cover letter has been copied to file QAPZCOVER member QSF98540.

 
Cause . . . . . : The cover letter has been copied to file QAPZCOVER in library GPL with member name of QSF98540 from file *N member *N.

 
Recovery . . . : Use the Display Program Temporary Fix (DSPPTF) command to display the cover letter. Specify product 5722SS1, PTF SF98540, release V5R4M0 and request cover letter only.

When using the default parameters for the SNDPTFORD command for PTF ordering, the SAVFs are downloaded by default to QGPL.
Other options would be to use:
  1. WRKOBJ OBJ(QGPL/QSI*) OBJTYPE(*FILE)
  2. WRKOBJ OBJ(QGPL/QSF*) OBJTYPE(*FILE)
  3. WRKOBJ OBJ(QGPL/QMF*) OBJTYPE(*FILE)
  4. WRKOBJ OBJ(QGPL/SI*) OBJTYPE(*FILE)
  5. WRKOBJ OBJ(QGPL/SF*) OBJTYPE(*FILE)
  6. WRKOBJ OBJ(QGPL/MF*) OBJTYPE(*FILE)
A message can usually be identified in the interactive joblog containing similar information about where the PTFs were downloaded after the request was successful.
Note: The PTFs will be found in the IFS, if the *IMAGE format was used, instead of the default *SAVF format.

 

IBM i, i5/OS and OS/400 level mapping

This table indicates which releases of IBM i, i5/OS or OS/400 are supported by each of the Power and System i models.

1 VxRxM5 of the Licensed Internal Code is required on the indicated models. Other models which support the release can utilize VxRxM5 LIC in place of VxRxM0 LIC, but it will not provide any functional advantage.

2 Release 6.1.1 of the Licensed Internal Code is required.

Wednesday, March 3, 2010

Controlling subsystem/library

1. Controlling subsystem/library, also known as QCTLSBSD, is a member of the restart category of i5/OS (TM) system values. You can use this system value to specify the controlling subsystem and the library.

Quick reference

Location In iSeries (TM) Navigator, select your system, --> Configuration and Service --> System Values --> Restart --> Setup

Special authority None

Default value Controlling subsystem - QBASE; Library - QSYS

Changes take effect At the next restart of the system

For more information on IPL, visit the information center link.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzal2/rzal2changeipl.htm

2. When the i5/OS® licensed program is first installed, QBASE is the default controlling subsystem. As the controlling subsystem, QBASE allocates system resources between the two subsystems QBASE and QSPL. Interactive jobs, communications jobs, batch jobs, and so on, allocate resources within the QBASE subsystem. Only spooled jobs are managed under a different subsystem, QSPL. This means you have less control of system resources for handling communications jobs versus interactive jobs than you would using the QCTL controlling subsystem.
Using the QCTL subsystem configuration, you have control of four additional subsystems for which the system has allocated storage pools and other system resources. Changing the QCTL subsystems, or creating your own subsystems gives you even more flexibility and control of your processing resources.