This action might not be possible to undo. Are you sure you want to continue?
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 1. DSPOBJAUT 2. GRTOBJAUT 3. EDTOBJAUT
• 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
. The job enters a job queue Job queues are work entry points for batch jobs to enter the system. the properties of a job are given to the job. A number of factors affect when the job is pulled off the job queue into the subsystem. like job priority on the job queue. • Life Cycle of a job in iSeries Submit a job Submitting a job to an iSeries server. the job will be pulled off the job queue to start running in the subsystem.• List printers available in the system WRKCFGSTS CFGTYPE (*DEV) CFGD (*PRT) • Adopted Authority -. where it is created and enters the system. When all of these factors work together. the job moves to the job queue where it waits to enter the subsystem. it moves to the job queue where it waits to enter the subsystem. They can be thought of as "waiting rooms" for the subsystem. At this time. and the maximum active jobs. the sequence number of the job queue. Once the job receives its job description and defines its properties.It adds authority of a program owner to the authority of the user running the program. Once the properties have been defined.
in that it controls how the output is made available to the print devices. 5. and the number of active jobs currently in the subsystem. The following information describes the different types of work entries and how to manage them. Auto start job entries Communication entries Job queue entries Prestart job entries work station entries . Specific types of work entries are used for different types of jobs. like the job description. 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 routing entry. Subsystems use different memory pools to support different types of jobs that run within them. the printer output from that job is sent to an output queue where it waits to be sent to a printer device or file. and the memory pool allocates memory for the job to run to completion. the maximum active jobs. The job uses several pieces of information before it can receive memory to run. The job finishes and moves to the output queue When a job finishes. The subsystem description. There are five types of work entries: 1. The subsystem gives the memory pool the information it needs to process the order in which jobs are allocated memory. it cannot run. Until a job gets its activity level and memory from a memory pool. 4. 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. The amount of memory from a memory pool. carries information. 2. 3. such as the memory pool to use. The output queue is like the job queue. as well as how many other jobs are competing for memory affect how efficiently a job runs.The job enters the subsystem When the job enters the subsystem it becomes active. Work entries are part of the subsystem description.
3.Hold job queue RLSJOBQ . Routing entries are stored in the subsystem description. The same is true on your system.) . 2. 8. A routing entry can be likened to a single entry in a shopping mall directory. 7. CRTJOBQ – Create job queue HLDJOBQ .Release job ENDJOB . 4.The routing entry identifies the main storage subsystem pool to use. Together.Clear job queue WRKJOBQ .End job CHGJOB – Change job WRKJOB – Work with job ( for spool file o/p and etc.• Routing Entries -. and from which class to get the run-time attributes. 5. Routing data identifies a routing entry for the job to use. 2. Routing entries consist of these parts: 1. 3. 5. and additional run-time information (stored in the class object). Routing entries in a subsystem description specify the program to be called to control a routing step for a job running in the subsystem. 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. HLDJOB – Hold job RLSJOB .Release job queue CLRJOBQ . which memory pool the job will use. 5. 4. 4.. Routing entries guide the job to the correct place. 3. Customers that cannot find the store they need may use a directory to help send them in the right direction. 6. routing entries and routing data provide information about starting a job in a subsystem. 2.Work with job queue (for job queue entries) Jobs are placed on a job queue with the command SBMJOB 1. 9. the controlling program to run (typically the system-supplied program QCMD).
Prestart job entries are defined within a subsystem. the type of program. • Pre start and auto start job Pre start job . The display includes information about the compiler. if your command says to check for active files.the priority of the job while executing JP . it will always be considered "active". Prestart jobs increase performance when you initiate a connection to a server. If you save a library as *PERM. then your backup has not been completing properly. • Run Priority Vs Job Priority RP .the relative order of the job waiting on job queue • DSPPGM Command The Display Program (DSPPGM) command displays information about a program. then the backup completed properly. If the date is an old date. or says not to check for active files.A prestart job is a batch job that starts running before a program on a remote system initiates communications with the server. and storage pool to use when the jobs are started.• 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. Prestart jobs become active . the type of program (ILE or OPM). certain processing attributes of the program. you must specify attributes for the subsystem to use to create and to manage a pool of prestart jobs. the size of the program. If the date is current. Most likely. Prestart jobs use prestart job entries in the subsystem description to determine which program. and the number of parameters that can be passed to the program when it is called. The best way to prove this is to do a DSPTAP OPTION(*PRINT) on the tape after the backup is complete. The next time you do a save to the same tape. Within a prestart job entry. class. your backup routine either reinitializes the tape. and check the dates next to each library. you would receive a message indicating that active files exist on the tape.
If you do not do this. If a problem occurs with this job. This job monitors for events sent when a STRTCP command has been issued. The daemon jobs then begin to listen on the .Autostart jobs are associated with iSeries host servers. Auto Start job . QZSOSIGN). Set the STRJOBS parameter to *YES. or they can be controlled with the Start Prestart Job (STRPJ) and End Prestart Job (ENDPJ) commands. the servers cannot start. If this job is not running. a file that is opened but never closed by one user of a prestart job remains open and available to the following user of the same prestart job. you must know the subsystem your prestart jobs are in (QUSRWRK or a user-defined subsystem) and the program (for example. to monitor prestart jobs for the signon server. your jobs will run in the default subsystem. For example. Otherwise. these resources will maintain the same status for the next user that uses the prestart job. Add your own pre-start job entries using the ADDPJE command. For example. the server daemon jobs can dynamically determine when TCP/IP has become active. even though the information may pertain to a prestart job that was started as a result of a sockets connection request. System information that pertains to prestart jobs (such as DSPACTPJ) uses the term 'program start request' exclusively to indicate requests made to start prestart jobs. 2. If you move jobs from the default subsystem. Use the Display Active Prestart Jobs (DSPACTPJ) command to monitor the prestart jobs. but there is no automatic cleanup for the prestart job once it has been used and subsequently returned to the pool. This means that resources that are used by one user of the prestart job must be cleaned up before ending use of the prestart job. Create your own subsystem description.when that subsystem is started. The subsystem will not end when the job disappears. Notes: * Prestart jobs can be reused. The QSYSWRK subsystem has an autostart job defined for all of the optimized servers. This way. The QSERVER subsystem has an autostart job defined for the file server and database server jobs. The number of times the prestart job is reused is determined by the value specified for the maximum number of uses (MAXUSE) value of the ADDPJE or CHGPJE CL commands. you must: 1. you may want to end and restart the QSERVER subsystem.
Subsystems manage resources. one subsystem may be set up to handle only interactive jobs. For example. The run-time characteristics of a subsystem are defined in an object called a subsystem description.appropriate ports. The system can contain several subsystems. and TCP/IP is started while the host servers are active. For instance. with the exception of system jobs. It is identified in the Controlling subsystem/library (QCTLSBSD) system value. you must start the controlling subsystem again. To end this condition. including the controlling subsystem are ended.The subsystem is where work is processed on the system. and it is the subsystem through which the system operator controls the system via the system console. You can end each subsystem individually or you can use the ENDSBS SBS(*ALL) OPTION(*IMMED). the following sequence of commands must be issued in order to start using TCP/IP: • AS 400 Subsystem -. The controlling subsystem The controlling subsystem is the interactive subsystem that starts automatically when the system starts. Only one controlling subsystem can be active on the system at any time. All jobs. while another subsystem handles only batch jobs. Subsystems can also be designed to handle many types of work. If the autostart job is not active. predefined operating environment through which the system coordinates the work flow and resource use. all operating independently of each other. and only one workstation is active. most of the activity on the system has ended. When the system is in the restricted condition. When all of the subsystems. A subsystem is a single. Each subsystem can run unique operations. a restricted condition is created. Some programs for diagnosing equipment problems also require the system to be in a restricted condition. The system allows you to decide the number of subsystems and what types of work each subsystem will handle. IBM® supplies two complete controlling subsystem descriptions: QBASE (the default controlling subsystem) and QCTL. The system must be in this condition for commands such as Save System (SAVSYS) or Reclaim Storage (RCLSTG) to run. if you want to permanently change the amount of work (number of jobs) coming from a job queue into a subsystem you only need to change the job queue entry in the subsystem description. run within subsystems. Note: There is also a batch restricted state in which one batch job can be active. .
and . The ENDSYS and ENDSBS functions will send a CPI091C information message to the command issuer when this condition is detected. Like a set of detailed blueprints. suspended group jobs. Sometimes it may appear as though there is a single job remaining. how much work the subsystem can handle. A subsystem description defines how. each subsystem description is unique. An active subsystem takes on the simple name of the subsystem description. or you can create your own. you need to end them in order for the system to reach the restricted state. but the system does not go into the restricted state. Specific types of work entries are used for different types of jobs. When you create a subsystem. containing the specific characteristics that describe the subsystem. the controlling program to run (typically the system-supplied program QCMD). where. Work entries Work entries identify the sources where jobs can enter a subsystem. how much main storage (memory) will be used. and how much work enters a subsystem.Important: The system cannot reach the restricted state until there is only one job remaining in the controlling subsystem. Routing entries The routing entry identifies the main storage subsystem pool to use. and which resources the subsystem uses to perform the work. You can use a subsystem description supplied with your system (with or without making changes to it). and how quickly jobs in the subsystem can run. the first step is to define the subsystem attributes. Work entries are part of the subsystem description. Subsystem description attributes Subsystem description attributes are common overall system attributes. The description includes where work can enter the subsystem. Subsystem description A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. If these jobs exist. or disconnected jobs on the remaining active display. In this case you need to verify that there are no suspended system request jobs. Use the Work with Active Jobs (WRKACTJOB) command and press F14=Include to display any suspended or disconnected jobs. The systemrecognized identifier for the object type is *SBSD.
You can also use this concept to move less important applications or data to your older. you do not generally need to worry about partitioning high-growth databases. Disk defragmentation software manages logical file fragmentation of the hard disk images. Storage pools: Administrators manage storage through the concept of storage pools. numbered 2-16. or disk striping on your Integrated Netfinity Server. The system ASP is ASP 1. slower disk drives. Because of the way AS/400 manages disk data. cylinders. including spreading the hard disk images across multiple drives and applying RAID and file mirroring (if configured). the operating system that runs on an AS/400. Disk protection: AS/400 disks can be protected in two ways: . This pool is called an auxiliary storage pool (ASP). does not need to deal directly with disk drives. You can use storage pools to distribute your AS/400 data over several groups of disks. Needed objects are copied ("paged in") from this address space on disk into the address space of main memory. Routing entries are stored in the as400 subsystem description. Because AS/400 storage management handles these tasks. defragmenting disks. • AS400 Storage Management OS/400 and disk drives: OS/400. The Integrated Netfinity Server uses device drivers to share the AS/400's disk drives.additional run-time information (stored in the class object). You can configure additional user ASPs. Every system has at least one ASP. running a defragmentation program on the Integrated Netfinity Server helps only in cases where "critical file system structures" can be defragmented. Beneath the operating system a level of software (called System Licensed Internal Code (SLIC)) "hides" the disk drives and manages the storage of objects on those drives. AS/400 storage management handles the hard disks. the system ASP. A virtual address space is mapped over the existing disk space and used for addressing objects rather than disk drive IDs. You can logically join disk units to form a storage pool and place objects into this pool. and sectors. These device drivers send and receive disk data to the AS/400 storage management subsystem.
AS/400 performs write operations on both disks at the same time. and with it one set of disks. Mirroring Mirroring keeps two copies of data on two different disks. you can attach the mirrored disks to two different disk controllers. If a disk fails. AS/400 can rebuild the information from the failed disk on the new (and therefore empty) disk. depending on how important their availability is. When you replace the failing disk. When you replace the failing disk with a new one. If one disk fails. . Then if one controller fails. You can define storage pools on your AS/400 to have different levels of protection or no protection at all. Each disk holds checksum information of the other disks in the same array. the RAID-5 disk controller can re-create the data of the failing disk with the help of the checksum information on the other disks. On larger models of AS/400. and can simultaneously perform two different read operations on the two disks of a mirrored pair. To further increase the level of protection. Attaching the two disk controllers that form a mirrored pair to two different buses increases availability even more. Then you can put applications and data into a storage pool with the right amount of protection. you can attach controllers to more than one bus. AS/400 uses information from the second disk.RAID-5 The RAID-5 technique groups several disks together to form an array. the other controller can keep the system up. AS/400 copies the data from the intact disk to the new disk.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.