Authorization List

Create authorization list -- CRTAUTL Securing objects with authorization list -- EDTOBJAUT -- If u r using authorization list for securing objects change the public authority to *AUTL Add users to authorization list -- EDTAUTL or -- ADDAUTLE Checking authorization list -- DSPAUTL (displays all the user authorities to the list) -- F15 lists all the objects secured by the list

Group Profile
By creating a group profile, you can authorize one user profile to a number of programs or files and then have other users "inherit" those authorizations by assigning them as members of that group profile. Group profiles centralize security by limiting access to the lowest possible number of users (one), while retaining the flexibility to have any number of users access those security settings. To achieve the functionality of group profile, first we create a user profile which later will be treated as group profile and this profile (group profile) will be inherited by other user profiles that are being created on the system. If the group profile name has a hash in it, then authority given to it is not picked by members of that group profile.

Logged in users in the server

WRKUSRJOB USER (*ALL) STATUS (*ACTIVE) JOBTYPE (*INTERACT) -- we can find the logged in users by typing the above command, because one interactive job is there for each logged in users in the system

 List printers available in the system

WRKCFGSTS CFGTYPE (*DEV) CFGD (*PRT)

Adopted Authority
-- It adds authority of a program owner to the authority of the user running the program.

Life Cycle of a job in iSeries

Submit a job Submitting a job to an iSeries server, where it is created and enters the system. At this time, the properties of a job are given to the job. Once the properties have been defined, the job moves to the job queue where it waits to enter the subsystem. Once the job receives its job description and defines its properties, it moves to the job queue where it waits to enter the subsystem.

The job enters a job queue Job queues are work entry points for batch jobs to enter the system. They can be thought of as "waiting rooms" for the subsystem. A number of factors affect when the job is pulled off the job queue into the subsystem, like job priority on the job queue, the sequence number of the job queue, and the maximum active jobs. When all of these factors work together, the job will be pulled off the job queue to start running in the subsystem.

The job enters the subsystem When the job enters the subsystem it becomes active. Until a job gets its activity level and memory from a memory pool, it cannot run. The job uses several pieces of information before it can receive memory to run. The subsystem description, like the job description, carries information, such as the memory pool to use, the routing entry, the maximum active jobs, and the number of active jobs currently in the subsystem.

The memory pool allocates memory to the subsystem Memory is a resource from the memory pool that the subsystem uses to run the job. The amount of memory from a memory pool, as well as how many other jobs are competing for memory affect how efficiently a job runs. Subsystems use different memory pools to support different types of jobs that run within them. The subsystem gives the memory pool the information it needs to process the order in which jobs are allocated memory, and the memory pool allocates memory for the job to run to completion.

The job finishes and moves to the output queue When a job finishes, the printer output from that job is sent to an output queue where it waits to be sent to a printer device or file. The output queue is like the job queue, in that it controls how the output is made available to the print devices. The output queue allows the user to control what files are printed first.

Work Entries
Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem description. The following information describes the different types of work entries and how to manage them. There are five types of work entries: 1. 2. 3. 4. Auto start job entries Communication entries Job queue entries Prestart job entries

5. work station entries

Routing Entries -- The routing entry identifies the main storage subsystem pool to use, the
controlling program to run (typically the system-supplied program QCMD), and additional run-time information (stored in the class object). Routing entries are stored in the subsystem description. A routing entry can be likened to a single entry in a shopping mall directory. Customers that cannot find the store they need may use a directory to help send them in the right direction. The same is true on your system. Routing entries guide the job to the correct place. Routing entries in a subsystem description specify the program to be called to control a routing step for a job running in the subsystem, which memory pool the job will use, and from which class to get the run-time attributes. Routing data identifies a routing entry for the job to use. Together, routing entries and routing data provide information about starting a job in a subsystem. Routing entries consist of these parts: 1. 2. 3. 4. 5. 6. 7. 8. 9. The subsystem description Class Comparison data Max: active routing steps Memory pool ID Program to call Thread resources affinity Resources affinity group The sequence number

Job related commands

1. 2. 3. 4. 5. CRTJOBQ Create job queue HLDJOBQ - Hold job queue RLSJOBQ - Release job queue CLRJOBQ - Clear job queue WRKJOBQ - Work with job queue (for job queue entries)

Jobs are placed on a job queue with the command SBMJOB 1. 2. 3. 4. HLDJOB Hold job RLSJOB - Release job ENDJOB - End job CHGJOB Change job

5. WRKJOB Work with job ( for spool file o/p and etc..)

EXPDATE=*PERM parameter in SAVLIB command

The expiration date parameter tells the AS/400 how long to consider the backup to be an "active" file. If you save a library as *PERM, it will always be considered "active". The next time you do a save to the same tape, if your command says to check for active files, you would receive a message indicating that active files exist on the tape. Most likely, your backup routine either reinitializes the tape, or says not to check for active files. The best way to prove this is to do a DSPTAP OPTION(*PRINT) on the tape after the backup is complete, and check the dates next to each library. If the date is current, then the backup completed properly. If the date is an old date, then your backup has not been completing properly.

Run Priority Vs Job Priority

RP - the priority of the job while executing JP - the relative order of the job waiting on job queue

DSPPGM Command
The Display Program (DSPPGM) command displays information about a program. The display includes information about the compiler, the type of program, certain processing attributes of the program, the type of program (ILE or OPM), the size of the program, and the number of parameters that can be passed to the program when it is called.