Preventing Startup Program from Running

In the QCTL controlling subsystem, there is an auto job entry called QSTRUPJD. It runs as soon as the QCTL is started. In the QSTRUPJD job description, a request data CALL QSYS/QWDAJPGM retrieves system value QSTRUPPGM. The program that is specified in the system value will run. If system value QSTRUPPGM is set to *NONE, there is no startup program to call.

To change the system value, on the operating system command line type the following:

CHGSYSVAL SYSVAL(QSTRUPPGM) VALUE(*NONE)

Press the Enter key.

The help text on the operating system for the system value includes the following:

A change to this system value takes effect the next time the system is IPLed. The shipped value is QSYS/QSTRUP.

Can IASP data be saved in Restricted system state?

If the system is in restricted state, it is possible to save the security data by using the command SAVSECDTA ASPDEV(*ALLAVL). This command will save the private authorities for all available IASPs.

To save the IASP at V5R2, it must be in AVAILABLE or ACTIVE status. The IASP status changes from AVAILABLE to ACTIVE when all subsystems are closed because the jobs that service the ASP are under QSYSWRK.

Starting from V5R3, it is possible to save the IASP only if it is in AVAILABLE status. This does not mean that the security data cannot be saved if the system is in restricted status because if the IASP is AVAILABLE before the closure of all subsystems, the status will not be changed to ACTIVE any more. In fact, the jobs that service the IASP are system jobs that are no longer under subsystem QSYSWRK, so they will not be ended any more when going to restricted state.

Starting of TCP/IP Interface Fails with Message TCP1B01

When using the STRTCPIFC command, or when trying to start a TCP/IP interface from the NETSTAT or CFGTCP menus, the start attempt times out with error message TCP1B01. The message reads:

Message ID . . . . . . . . . : TCP1B01

Message file . . . . . . . . : QTCPMSG

Library . . . . . . . . . : QSYS

Message . . . . : Unable to determine if &1 interface started.

Cause . . . . . : The QTCPIP job in the QSYSWRK subsystem is not active, or the default wait time for your job was exceeded while waiting for the interface to start.

Recovery . . . : Use the Work with Active Jobs (WRKACTJOB) CL command to list the active jobs in the QSYSWRK subsystem. If the QTCPIP job is not active, issue the End TCP/IP (ENDTCP) CL command followed by the Start TCP/IP (STRTCP) CL command. After STRTCP completes processing, issue the Start TCP/IP Interface (STRTCPIFC) CL command again. If the QTCPIP job in the QSYSWRK subsystem is active, continue to look in the QTCPIP job log to determine if the &1 interface was started. To avoid this problem when using STRTCPIFC, wait for system activity to decrease, or increase the default wait time for your job using the Change Job (CHGJOB) CL command.

Despite the recovery action listed, the problem can actually be due to authority issues. When using the WRKJOB command on the QTCPIP job (WRKJOB QTCPIP), it is possible to see no active QTCPIP jobs. Working with the most recent job in OUTQ status, and reviewing the joblog, it is very likely that message CPFA09C is posted in the joblog. Typically this message refers to an object named QLGPGCMA.LOCALE. However, the message can vary. It is very possible that the object is an Integrated File System object and is potentially the root directory ('/'). Verify the root directory's authority by using the command WRKLNK OBJ('/') or verify the authority to the object identified in the error message. Use Option 9 to view the authority, and ensure *PUBLIC is not set to *EXCLUDE.

How to FTP a Save File Stored in the IFS to a Library on the Same System

To FTP a save file stored in the IFS to a library on the same system, you should perform the following steps:

1. Create a save file that has the same name as the save file stored in the IFS in the library of your choice.
CRTSAVF FILE(YOURLIB/YOURSAVF)
Note: Replace YOURSAVF with the name of the savf stored in the IFS. Replace YOURLIB with the library you would like the savf stored in.
2. On a command line, FTP to the current system you are logged onto:
FTP sysname
Note: Replace sysname with the name or IP address of your system.
3. Use the following example as a guide for the FTP prompts. In this example, replace the following information with your information:
USERID = Your IBM i user ID
/IFSDIRECTORY/YOURSAVF = The path to the IFS directory containing the savf
YOURLIB/YOURSAVF = The library and savf you specified in Step 1
File Transfer Protocol
Previous FTP subcommands and messages:
Connecting to host sysname.domain at address x.x.x.xxx using port 21.
220-QTCP at sysname.domain.
220 Connection will close if idle more than 15 minutes.
> USERID
331 Enter password.
230 USERID logged on.
OS/400 is the remote operating system. The TCP/IP version is "V6R1M0".
250 Now using naming format "0".
257 "QGPL" is current library.
> bin
200 Representation type is binary IMAGE.
> quote site namefmt 1
250 Now using naming format "1".
> get /IFSDIRECTORY/YOURSAVF YOURLIB/YOURSAVF (REPLACE
229 Entering Extended Passive Mode (13492).
150 Retrieving file /IFSDIRECTORY/YOURSAVF
226 File transfer completed successfully.
42240 bytes transferred in 0.046 seconds. Transfer rate 920.293 KB/sec.

4. The save file should now be stored in YOURLIB/YOURSAVF. You can issue a DSPSAVF YOURLIB/YOURSAVF to verify the contents of the savf and use RSTxxx commands to restore the contents of the savf.

Sending Data to IBM System i5 Software Support

To send data to IBM System i5 Software Support, the data must be in ASCII text. The best way to get the file from the system is to use IBM iSeries Navigator to pull the files down to your PC. Highlight the files QSYSPRT and QPCSMPRT, as in the following print screen. (You might have only one of these files.) Then drag the files to your desktop (only the drag operation is supported).

To send the files to IBM Remote Technical Support, do the following:

1. Use a data compression utility such as PKZIP, PKZIP for Microsoft Windows, or WinZip to create a single binary file containing all of the data that must be sent to the Rochester Support Center. After dragging the files to your desktop, open the text file in Notepad: Top left of Notepad:

- Select File

- Select Save AS

- Change Encoding from UNICODE to ANSI

Note: When changing the encoding, this cuts most file sizes in half. To make sure you have the correct file name:

- Create a new folder

- xxxxx.bbb.ccc.yyy.yyy

- Drag the file(s) to the folder

- Zip or compress the folder

where xxxxx is the PMR number, bbb is the branch number, ccc is the country code (such as 12345.7TD.000), and yyy.yyy is a short description for the folder (such as 12345.ZIP or 12345.7TD.000.12345.ZIP for a zip file, or 12345.SAVF or 12345.7TD.000.12345.SAVF for a save file downloaded from the system).

2. After you have created the ZIP file, you can send it to your Rochester Support Center representative using FTP or e-mail.

3. To send the ZIP file using e-mail, contact your Rochester Support Center representative and get his or her e-mail address. Then attach the file to the e-mail and send it to their e-mail address. Specify the PMR in the subject line of the e-mail.

There is a 10 MB limit for attachments when sending an e-mail to IBM. If the file is larger than 10 MB, use the FTP option specified in Step 4. Otherwise, skip to Step 5.

4. To send the file using FTP, use an FTP program to upload the file in binary format to testcase.boulder.ibm.com in folder toibm/os400 and login using the anonymous user ID and your e-mail address as the password, or bring up a Windows command prompt and type the following commands:

ftp testcase.boulder.ibm.com

user anonymous

password (for example, your e-mail address)

cd toibm/os400

bin

put xxxxx.bbb.ccc.yyy.yyy

quit

where xxxxx is the PMR number, bbb is the branch number, ccc is the country code (such as 12345.7TD.000) and yyy.yyy is a short description for the file type (such as 12345.ZIP or 12345.7TD.000.12345.ZIP for a zip file, or 12345.SAVF or 12345.7TD.000.12345.SAVF for a save file downloaded from the system).

The testcase.boulder.ibm.com FTP site can also be accessed through a Web browser at ftp://testcase.boulder.ibm.com/ or https://testcase.boulder.ibm.com/.

5. After the file has been successfully sent or uploaded, notify your Support Center representative so they know to expect it.

Saving and Restoring All TCP/IP Configuration Files

Saving just the physical configuration files and then restoring them can cause problems. This is because the logical files, which are used by different functions to access the data stored in the physical files, point to the renamed physical file if just the physical file is restored. The renamed physical file, which is created by the restore database functions, maintains the indexes to the logical files. Another reason to save and restore the configuration files as a group is that there are some dependencies between some of the files. Saving and restoring just a subset of the files could also cause problems, especially when activating TCP/IP processing.

One method to save all TCP/IP files (logical and physical) is to type the following commands:
SAVOBJ OBJ(QATOC*) LIB(QUSRSYS) DEV(*SAVF) OBJTYPE(*FILE) SAVF(yourlib/yoursavf)

SAVOBJ OBJ(QATM*) LIB(QUSRSYS) DEV(*SAVF) OBJTYPE(*FILE) SAVF(yourlib/yoursavf)

To restore all TCP/IP files on the system, use the following commands:

RSTOBJ OBJ(QATOC*) SAVLIB(YOURLIB) DEV(*SAVF) OBJTYPE(*FILE) SAVF(yourlib/yoursavf) MBROPT(*ALL) + ALWOBJDIF(*ALL)

RSTOBJ OBJ(QATM*) SAVELIB(QUSRSYS) DEV(*SAVF) OBJTYPE(*FILE) SAVF(yourlib/yoursavf) MBROPT(*ALL) + ALWOBJDIF(*ALL)

After the restore is complete, there is some required cleanup. Begin by issuing the following command:

WRKOBJ OBJ(QUSRSYS/QATOC*)

After the command has been issued, complete the following steps:

1 Delete all of the old logical files that are named QATOCL00xx (with object description of 'Old name...').
2 Delete all of the old physical files that are named QATOCX00xx (with object description of 'Old name...').

Listing Last Used Date / Creation Date for all Objects in a Library

Dump all objects in selected library to an outfile:

DSPOBJD OBJ(TESTLIBRARY/*ALL) OBJTYPE(*ALL) OUTPUT(*OUTFILE) OUTFILE(QGPL/OBJDOUT)
Start SQL so we can select the necessary fields in the outfile:
STRSQL
Paste the following:
SELECT ODOBNM, ODLBNM, ODOBTP, ODUDAT, ODCDAT FROM qgpl/OBJDOUT
ORDER BY ODUDAT desc
This will create a display with objects creation date and last used date. You can also print to an outfile by using F13 on the Enter SQL Statements screen and changing the session attributes to print.

System Values - Printing

Use the Work with System Value (WRKSYSVAL) command to get a printout of the system values. From an IBM OS/400 or IBM i5/OS command line, type the following:

WRKSYSVAL

Press F4 (to prompt), and specify *PRINT for the OUTPUT parameter. This creates a spooled file that can be printed.

Displaying the Main Storage Size

To display the main storage size, use the Work with Shared Pool (WRKSHRPOOL) command. The main storage size is displayed at the top of the screen.

Getting a Listing of All User Profiles Including a Text Description

To generate a listing of all user profiles, on the operating system command line type the following:


DSPOBJD OBJ(*all) OBJTYPE(*usrprf) OUTPUT(*print)
Press the Enter key.

Startup program prevention

In the QCTL controlling subsystem, there is an auto job entry called QSTRUPJD. It runs as soon as the QCTL is started. In the QSTRUPJD job description, a request data CALL QSYS/QWDAJPGM retrieves system value QSTRUPPGM. The program that is specified in the system value will run. If system value QSTRUPPGM is set to *NONE, there is no startup program to call.

To change the system value, on the operating system command line type the following:

CHGSYSVAL SYSVAL(QSTRUPPGM) VALUE(*NONE)

Press the Enter key.

System Name Changing Process

Use the Change Network Attributes (CHGNETA) command to change the system name.

CHGNETA SYSNAME(new system name)

LCLCPNAME(Local control point) (May need to be changed also)

LCLLOCNAME(Default local location) (May need to be changed also)

Note: This command requires *ALLOBJ authority.

The name can contain up to 8 alphanumeric characters. The name entered becomes the current system name at the next IPL.

It is important to remember that the Local Control Point Name (LCLCPNAME) and Default Local Location Name (LCLLOCNAME) are used rather than the SYSNAME when setting up SNA communications with APPN. Take this into consideration when changing the SYSNAME because the LCLCPNAME and LCLLOCNAME may also require changes.

Making Only One Batch Job Run at a Time

The number of batch jobs running can be controlled at the job queue level, the subsystem level, or the pool level. Do one of the following: o For the job queue level, set the MAXACT parameter on the Change Job Queue Entry (CHGJOBQE) command.


o For the subsystem level, set the MAXJOBS parameter on the Change Subsystem Description (CHGSBSD) command.

o For the pool level, the manner of changing the maximum number of jobs is a function of whether a private pool is being used or a shared pool. Which pool a particular job runs in is a function of how it is routed; thus, it is a function of the routing data specified when the job is submitted and the routing entries in the subsystem description for the subsystem that is servicing the job queue that the batch job is submitted to. If the pool is a private pool defined to and used only by that subsystem, the activity level is specified for the pool when the subsystem description is created or by using the CHGSBSD command to change the activity level. If the pool is a shared pool, the activity level of the pool is changed by use of the CHGSHRPOOL command or the WRKSHRPOOL command.

Finding Job Logs

There are a couple commands to choose from. If you know exactly what job log you are looking for, run one of the following commands:

DSPJOBLOG job#/user/jobname

or

DSPJOB job#/user/jobname

The DSPJOB command will allow you to display that job in OUTQ, JOBQ, or active status.

If you know only the user ID of the job log you want to find, issue the following command:

WRKUSRJOB user id

The WRKUSRJOB command will show you all jobs in JOBQ, OUTQ, or active status submitted under that user ID.

If you know the name the job runs under, issue the following command:

WRKJOB job name (WRKJOB QSTRUPJD)

The WRKJOB command will allow you to work with all jobs that run under that job name which are active, sitting in a JOBQ or in an OUTQ.

If the job log does not contain enough information, or is not even being generated, check how the logging level in the job description is set up. This can be found on the user profile submitting the job. To get the most information you can in a job log, we suggest you set the parameters to the following:

Message logging:

Level . . . . . . . . . . . . . . . . . . . . : 4

Severity . . . . . . . . . . . . . . . . . . . : 0

Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL

Log CL program commands . . . . . . . . . . . . : *YES

Keep in mind that if you change these parameters, job logs will start being produced for every job that runs under that job description, even the ones that end normally. This can cause unnecessary print jobs to active writers or fill up OUTQs quickly. So, you may want to check and possibly change the OUTQ that the job logs will get routed to. One recommendation is to send them to the QEZJOBLOG OUTQ. To do this, change the QPJOBLOG print file to direct it to that OUTQ with the CHGPRTF QPJOBLOG command. The parameters you want to look for are hidden deep into the file description. You may have to page down five times to get to the following fields:

Change Printer File (CHGPRTF)

Type choices, press Enter.

Spool the data . . . . . . . . . *YES *SAME, *YES, *NO

Spooled output queue . . . . . . QEZJOBLOG Name, *SAME, *JOB, *DEV

Library . . . . . . . . . . . QUSRSYS Name, *LIBL, *CURLIB

Form type . . . . . . . . . . . *STD Character value, *SAME, *STD

Copies . . . . . . . . . . . . . 1 1-255, *SAME

Then, set up the GO CLEANUP menu to automatically clear that OUTQ of job logs after determining the number of days you wish to keep them on the system.

Let us take a tour through a job log......

Job: QTGTELNETS User . . : QTCP Number . . . : 104878

* Job 104878/QTCP/QTGTELNETS started on 06/18/98 at 09:33:32 in subsystem

QSYSWRK in QSYS.* Job entered system on 06/18/98 at 09:33:32.

Job 104878/QTCP/QTGTELNETS submitted.

Library QGPL added to library list.

Vary on completed for device QPADEV0363.

Every job on the operating system starts with the CPF1124 message. We can see the additional information by pressing F1 in the job log on the first message:

Message ID . . . . . . : CPF1124 Severity . . . . . . . : 00

Message type . . . . . : Information

Date sent . . . . . . : 06/18/98 Time sent . . . . . . : 09:33:32

Message . . . . : Job 104878/QTCP/QTGTELNETS started on 06/18/98 at 09:33:32 in subsystem QSYSWRK in QSYS. Job entered system on 06/18/98 at 09:33:32.

This brings up one very common misconception. All this means is that the job was submitted successfully in subsystem QSYSWRK for user QTCP. It does not mean the job actually processed anything, but that the routing step to submit the job to a subsystem did not run into any errors entering the subsystem. If the job submits and completes within seconds or ends abnormally, you would want to work with the fully qualified job name listed in the job log to find out any other errors that occurred. Quite often, we have programs/commands that run under a different user profile to ensure proper authority. For an example of this, issue the STRHOSTSVR command.

Job . . : QPADEV0020 User . . : XZY3226 Number . . . : 032060

Routing entry sequence number 2539 already exists.  Compare value conflicts with routing entry 2539.

Job 032068/QUSER/QZRCSRVSD submitted to job queue QSYSNOMAX in library  QSYS.

Start of prestart jobs in progress.

Routing entry sequence number 2540 already exists.

Compare value conflicts with routing entry 2540.

Job 032070/QUSER/QZSOSGND submitted to job queue QSYSNOMAX in library QSYS.

Start Prestart Jobs command is not allowed now.

Routing entry sequence number 200 already exists.

Compare value conflicts with routing entry 200.

Job 032071/QUSER/QPWFSERVSD submitted to job queue QPWFSERVER in library QSYS.

If we wanted to work with the job associated with the host server command, we would write down the information from our job log for the Job 032071/QUSER/QPWFSERVSD.

Issue a WRKJOB JOB(032071/QUSER/QPWFSERVSD) and you will see:

Job . . : QPWFSERVSD User . . : QUSER Number . . . : 032071

Job 032071/QUSER/QPWFSERVSD started on 06/23/98 at 09:18:40 in subsystem QSERVER in QSYS. Job entered system on 06/23/98 at 09:18:38. Job 032071/QUSER/QPWFSERVSD submitted.

The protocol required to support the specified address family is not available at this time.

HOST SERVER COMMUNICATIONS ERROR OCCURRED ON SOCKET - SPX FAMILY.

Back to our job log.....when trying to locate what JOBQ a job was submitted to:

Job: QTGTELNETS User . . : QTCP Number . . . : 104878

Job 104878/QTCP/QTGTELNETS started on 06/18/98 at 09:33:32 in subsystem QSYSWRK in QSYS. Job entered system on 06/18/98 at 09:33:32. * Job 104878/QTCP/QTGTELNETS submitted. *

Library QGPL added to library list.

Press F1 in the job log to the job submitted message which is a CPI1125.

Message ID . . . . . . : CPI1125 Severity . . . . . . . : 00

Message type . . . . . : Information

Date sent . . . . . . : 06/18/98 Time sent . . . . . . : 09:33:32

Message . . . . : Job 104878/QTCP/QTGTELNETS submitted.

Cause . . . . . : Job 104878/QTCP/QTGTELNETS submitted to job queue

QSYSNOMAX in QSYS from job 104697/QTCP/QTGTELNETS. Job 104878/QTCP/QTGTELNETS was started using the Submit Job (SBMJOB) command with the following job attributes:

JOBPTY(5) OUTPTY(5) PRTTXT()

RTGDTA(TELNETS) SYSLIBL(SST QTODSYS QSYS QHLPSYS QUSRSYS

QSPTLIB SECLIBV3R1 OSLSYS) CURLIB(QTCP) INLLIBL() LOG(4 00 *SECLVL)

LOGCLPGM(*NO) INQMSGRPY(*RQD) OUTQ(/*DEV) PRTDEV(PRT01) HOLD(*NO)

DATE(*SYSVAL) SWS(00000000) MSGQ(QUSRSYS/QTCP) CCSID(65535) SRTSEQ(*N/*HEX)

LANGID(ENU) CNTRYID(US).

The end of a job......

Message CPF1164 is the message issued after the job completes along with the ending code, indicating if the end was either normal or abnormal.

End codes and their meanings are as follows:

0 The job completed normally.

10 The job completed normally during controlled ending or controlled subsystem ending.

20 The job exceeded end severity (ENDSEV job attribute).

30 The job ended abnormally.

40 The job ended before becoming active.

50 The job ended while the job was active.

60 The subsystem ended abnormally while the job was active.

70 The system ended abnormally while the job was active.

80 The job ended (ENDJOBABN command).

90 The job was forced to end after the time limit ended (ENDJOBABN command).

If you are still unable to locate a job log, you can try locating the job information in the history log. To look at the history log, from an operating system command line, type the following:

DSPLOG LOG(QHST) MSGID(CPF1164)

Press the Enter key. You can search for a specific message ID in the history log by prompting (F4) on the DSPLOG QHST command, pressing F10 for additional information, pressing the page down, and typing in the message ID. You can also narrow down your search by specifying a date and time range.

Changing the Options in System Request

It is possible to change some of the options shown in System Request. You cannot change the options as they appear on the panel, but you can change the commands that those options call.

Suppose you would prefer that SYS REQ, Option 3, perform a WRKJOB command rather than a DSPJOB command. Do the following:

1 On an operating system command line, type the following:
WRKMSGD CPX2313
Press the Enter key.
2 Type 2 under OPT, next to CPX2313. Press the Enter key.
3 You are on the CHGMSGD screen. The options performed by SYS REQ are shown on the First-level message text line; for example, you will see the following:
First-level message text . . . . 'ENDRQS DSPJOB DSPMSG SNDMSG SIGNOFF DSPMSG DSCJOB DSPWSUSR ENDRDBRQS '
SYS REQ, Option 1, does a TFRSECJOB command, which is not in the text. Therefore, you cannot change that. For the others, the commands performed by SYS REQ are as follows:

1. Display sign on for alternative job . . . . . TFRSECJOB
2. End previous request . . . . . . . . . . . . . . ENDRQS
3. Display current job. . . . . . . . . . . . . . . DSPJOB
4. Display messages . . . . . . . . . . . . . . . . DSPMSG
5. Send a message . . . . . . . . . . . . . . . . . SNDMSG
6. Display system operator messages. . . . .DSPMSG QSYSOPR
7. Display work station user. . . . . . . . . . . DSPWSUSR
80. Disconnect job. . . . . . . . . . . . . . . . . DSCJOB
90. Sign off . . . . . . . . . . . . . . . . . . . .SIGNOFF

If the command you want to change can be matched to a command in the First level message text line, you can change the command by substituting a different command. It must be in exactly the same position as the original command; for example, the W in WRKJOB must be in exactly the same place as the D in DSPJOB was.

Fix Central Download Order Options

The first part of the download options screen for IBM i, i5/OS, and OS/400 allow the user to change the Order name to something more meaningful and whether to customize the order.

 
 
 
 
 
 
 
 
 
Note: If the option to Customize your order is not selected, the order will contain all PTFs related to the Cumulative, Groups, or individual PTFs selected. See the text beginning with To customize your order... in the Select download options screen above to see what will be removed from the order if customize is selected.

The second half of the screen allows the user to download individual fixes directly to the system, download virtual images using Download Director, download virtual images using FTP, or to order the fixes on media.

 
 
 
 
 
 
 
 
 
 
 
 
 
What will each option do? Download individual fixes directly to my system. Download individual fixes directly to my system. This option will allow the user to download fixes as save files directly down to the system. Selecting this option will lead next to the Download fixes to my system screen. The user will see a status bar noting the progress of the order.

If the order is not needed on the system, the user will get a summary similar to the following:

 
 
 
 

If the order is successful, the Order summary screen will note that the PTFs were successfully downloaded to the system.

Download virtual images using Download Director

This option allows the user to submit an order for virtual images. This will not result in an e-mail. When the order is ready, the user will need to utilize the Resume pending orders option.

After the order is submitted, the summary screen will note an approximate time when the order will be ready. When the order is ready, the user will need to select the Resume my pending orders from the order summary screen or from the panel on the right of the screen. The first section of the order shows Your order is being constructed.

Download virtual images using FTP

This option allows the user to submit an order for virtual images. This will result in two e-mails. The first e-mail will note that the order has been received. The second e-mail will not the link to the FTP site to download the order. The download summary will note Your order will be sent to the FTP server followed by the order details.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Order fixes on physical media (requires Software Maintenance Agreement)

This option takes you directly to the Order Fixes on Media site. If the user has a valid Software Maintenance Agreement with IBM, the option to mail the media rather than download the order can be selected.

If no Software Maintenance Agreement is available, the following screen will come up:

If Software Maintenance is found, the summary screen will note that the order will be mailed.

Note: For more on the download options, click on the appropriate link above.

Registering to Use Fix Central and Other IBM Web Sites

Before a user can access Fix Central and other IBM sites, registration must be completed. This document provides some information to assist users in obtaining a Web ID. If there are any problems with the registration process or with updating the Web ID, once created, please go to the Worldwide IBM Registration Helpdesk
When your registration is complete, this registration is part or all that is needed for access to the following sites:

1. Fix Central
2. Support for IBM System i5 
3. Entitled Software Support  
4. Software Service Request

Follow the steps for registering to have IBM id.
Open Software Service Request Link & Select the Register Now option at the right of any Sign in screen









Select the IBM Service Request option on the next screen to continue with the registration:

On the My IBM registration page, complete the general information that is noted with a red asterisk (*)

Click Continue
Complete the personal and business information that is marked by the red asterisk (*) on this page:

Note: At a minimum, fill in the preferred language, First name, Last name, daytime phone, company name,
Country/Region, Street address, City, State or Providence, and postal code (where appropriate)

Click Submit.

The next screen is a Thank you screen. Select Continue to complete the registration. (This step must be completed.)
Note: If Continue is not selected here, Fix orders will not complete using Fix Central nor will a user be able to submit electronic service requests or PMRs.

The user will be asked to sign in with the newly created user ID.



 
 
 
 
 
 
 
 
 
 
 
 
 

 

On the Request Access page, select the appropriate option and then complete the system information. This information includes the Customer number, Branch number, Machine type, and Machine serial number.

Note: If the customer number is not known, the user must talk to their Business Partner or IBM Marketing Representative.
For IBM System i products functions, only the iSeries profile section must be completed. However, the other sections can be completed if the data exists.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Select to search by Customer number or Serial number and fill in the Justification
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Step 3 in the request access steps is to verify the platform and IBM profile information:

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Choose to continue to finalize/complete the registration or update the IBM profile. The final screen indicates the registration is complete:

 
 
 
 
 
 
 
 
As indicated in the screen shot above, the registration takes approximately 5 minutes to complete for Fix Central use. However, if using this registration to work with PMRs on line, the wait is longer.

Adding a License Key for IBM OS/400 or IBM i5/OS

Starting with Version 4 of IBM® OS/400®, a license authorization code (also referred to as a key) must be installed on your system. Each system is assigned a unique license authorization code for every Version/Release/Modification of OS/400 or IBM® i5/OS®. To ensure continuous operation of your system, this code must be installed within 70 days after installing the Version/Release/Modification of OS/400 or i5/OS.

Name. . . . . . . . . . . . . : OS/400 Operating System
Product ID. . . . . . . . . . : 5722SS1
Version Release Modification. : V5R2M0
Code ID/Install Feature Number: 5050
Hardware Serial Number. . . . : 10-abcde
Processor Group . . . . . . . : *ANY
Usage . . . . . . . . . . . . : *NOMAX
License key . . . . . . . . . : 2EA13D 10C6D1 DCA901
CL installation command:
ADDLICKEY PRDID(5722SS1)
LICTRM(V5R2M0)
FEATURE(5050)
SERIAL(*LOCAL)
PRCGRP(*ANY)
LICKEY(2EA13D 10C6D1 DCA901)
USGLMT(*NOMAX)
EXPDATE(*NONE)
VNDDTA(*NONE)
Valid values for the characters in the LICKEY are A-F and 0-9 (no Ls and no Os).
To install the license key, run the CL command shown above. The ADDLICKEY command is shipped with public *EXCLUDE authority which requires *ALLOBJ authority to use the command. Normally, the security officer of the system has this authority.
Note: There are two other ways to add the license key:
1. Use Work with License Information (WRKLICINF) with Option 1. This will fill in the first several parameters and creates less chance for possible typing errors.
2. Go to the Entitled Software Support URL, find the appropriate license key, and then select the Install option.

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.

Setting Up Job Monitor using Management Central

It's very easy to setup the monitor for Jobs in the system. This monitor once configured and started can provide details pertaining to Job Name,Number, Start and end time and severl other required metrics like Disk I/O used, number of threads etc. Following are the steps for implementing the same.

1. Open iSeries Navigator
2. Click on Management Central to expand (Make sure Management Central Job is on your system otherwise connection to Management Central server will end.)

3. Right click on Job and select New Monitor, New Monitor dialog box will appear. Provide a name to Monitor and under tab Jobs to monitor, add the kind of jobs to be monitored one by one and proceed to next tab of Metrics.

4.  Select the metrics and proceed to Collection interval tab and specify the time interval for collection of different jobs metrics.

5. On the actions tab, select the available actions and proceed for Systems and Groups, and add the systems to be monitored. Once done, click ok and you will see a monitor created for you having a stopped status. Right click over monitor and select Start, once started, you can have the details based on the collection interval selected for all kinds of jobs.