SCF Reference Manual for the Kernel Subsystem

*BackupCPU.................Not Specified
*CPU.......................(00,01,02,03)
*DefaultVolume.............$SYSTEM.NOSUBVOL
*ExtSwap...................Not Specified
*Highpin...................ON
*HomeTerminal..............$TERM.#T1
*InFile....................$TERM.#T1
*Library...................Not Specified
*MemPages..................Not Specified
*Name......................$GP4nn
*OutFile...................$TERM.#T1
*PFSSize...................Not Specified
*PrimaryCPU................Not Specified
*Priority..................167
*Program...................$SYSTEM.SYSTEM.TACL
*SaveAbend.................OFF
*StartMode.................MANUAL
*StartupMessage............Not Specified
*StopMode..................Standard
*Type......................OTHER
*UserId....................SUPER.SUPER ( 255,255 )
2. A STATUS command shows that all instances of the object state are STOPPED:
-> STATUS PROCESS $ZZKRN.#GP
NONSTOP KERNEL - Status PROCESS \EAST.$ZZKRN.#PROCESS-A
Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
GP $GP400 STOPPED None None
GP $GP401 STOPPED None None
GP $GP402 STOPPED None None
GP $GP403 STOPPED None None
3. If necessary, use a TIMEOUT command (described in the SCF Reference Manual for G-Series
RVUs or the SCF Reference Manual for J-Series and H-Series RVUs) to specify a timeout value
that is larger than the default value of 90 seconds.
When you start a generic process that has been configured in multiple processors (by, for
example, the CPU ALL attribute), SCF might need more time to finish starting and reporting
about all instances of the generic process. This command allows time for the START command
that follows to start all instances of the generic process:
-> TIMEOUT
4. Start the process with a START command, For example:
KERNEL W00030 Process \EAST.$GP400 started
successfully.
KERNEL W00030 Process \EAST.GP401 started
successfully.
KERNEL W00106 One or more processes of \EAST.$ZZKRN.#GP did
not start due to cpu down. They will start when their CPU is
reloaded.
Two instances of the process did not start because their associated processors are down.
The TIMEOUT value stays in effect until the session ends or until you issue another TIMEOUT
command.
5. Verify that the status is now STARTED and that processes are running in the configured and
up processors, for example:
-> STATUS PROCESS $ZZKRN.#GP
NONSTOP KERNEL - Status PROCESS \EAST.$ZZKRN.#GP
54 Configuring and Managing Generic Processes