System Software Library Define Process Manual Abstract This manual describes the Define Process product, which is a background process used for defining, starting, stopping, and deleting a process in any network node to which the user has access. The manual contains information on the Define Process library and other capabilities of Define Process. This manual is intended for use by operators, system managers, and programmers.
Document History Edition Part Number Product Version Earliest Supported Release Published First 131360 Define Process G01 G01.00 December 1996 New editions incorporate any updates since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
Contents About This Manual v Notation Conventions vii 1. Introduction to Define Process Introduction 1-1 2. Process Definition Commands Introduction 2-1 Command Introduction 2-1 Define Process Command 2-2 _PCHECK Command 2-8 PHELP Command 2-11 PINFO Command 2-12 POUT Command 2-13 PSHOW Command 2-14 PSTART Command 2-15 PSTOP Command 2-15 TOSS Command 2-16 UNDP Command 2-16 WAIT Command 2-17 WAITREADY Command 2-18 Issuing Commands to a Defined Process 2-18 3.
Contents iv 131360 —Define Process Manual
About This Manual This is the first edition of the Define Process Manual. Originally, the Define Process product was a part of the ViewPoint product. The Define Process is an independent product now. This manual is an extract from the previous version of the ViewPoint Manual. Purpose of This Manual The Define Process commands described in this manual enable the user to define, start, stop, and remove a process in any network node to which the user has access.
Your Comments Invited vi About This Manual 131360 — Define Process Manual
Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable values that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets.
General Syntax Notation Notation Conventions An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Notation Conventions Notation for Messages !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ; !i !o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text.
Notation for Management Programming Interfaces Notation Conventions % Percent Sign. A percent sign precedes a number that is not in decimal notation. The %þnotation precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes a hexadecimal number. For example: %005400 P=%p-register E=%e-register Notation for Management Programming Interfaces UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown.
1 Introduction to Define Process Introduction The Define Process is a process that permits you to start up to 100 background processes such as PUP, FUP, SPOOLCOM without having to exit the process that you are currently working on. You must have access to the TACL process for using the Define Process utility. Operators at the TACL screen can communicate with command interpreters or other utilities and can use the Define Process commands to run several background processes simultaneously.
Introduction Introduction to Define Process queues. Commands to a process are queued in an input queue; responses from a process are queued in an output queue. Note. TACL must be a named process in order for you to use the Define Process command.
2 Process Definition Commands Introduction This section describes the syntax and semantics of the Define Process commands. The Define Process command library provides a set of commands to the TACL command interpreter. The library is available to you when you log on to your system in the same way as your other TACL library files. Command Introduction The commands in the Define Process library allow you to define, start, stop, and delete a process in any network node to which you have access.
Define Process Command Process Definition Commands Table 2-1. Define Process Commands (page 2 of 2) Command Description UNDP Removes a background process. WAIT Displays accumulated output from a background process and waits for the process to prompt for more input. WAITREADY Waits for a background process to prompt for more input. Caution.
Process Definition Commands Define Process Command DEBUG See the INSPECT option below. DEFMODE { OFF | ON } enables or disables the current TACL DEFINEs. It is the initial definition mode state for the new process. If omitted, TACL uses its current definition mode. Refer to the TACL Reference Manual for the current definition mode and for setting TACL DEFINEs. EXTSWAP specifies the volume and, optionally, the file name that is used for memory swaps of the process’s extended data, if there is any.
Define Process Command Process Definition Commands LIB [ file-name ] selects a user library file of object routines that is searched before the system library file to satisfy external references in the program being run. If you give the name of a library file, the program uses that library until you select another. The library file name is linked to the program file and remains in use for all runs of the program until you specify LIB without a file name.
Process Definition Commands Define Process Command the process. The current history number (surrounded by hyphens) appears to the left of the prompt of the process. NOSTART disallows starting the process after the process is defined. The process is started automatically when the first command is sent to the process or when you issue a PSTART command to it. NOWAIT sets that the default mode for commands to the process is NOWAIT. If you omit this option, the default mode is WAIT.
Define Process Command Process Definition Commands QUIET forces future PSTART commands not to print a message when starting the defined process. If this option is omitted, PSTART prints a starting verification message when it is starting the process. (The message can be useful to see when a process is being recreated after being stopped for any reason—such as an unintentional command error.
Process Definition Commands • Define Process Command The default symbolic name of a defined process is the file-name portion of the process program file name. For example, this command defines a PERUSE process with the symbolic name of PERUSE: > DP PERUSE It might not be desirable to use a symbolic name for a defined process that is the same as the name of a utility, such as PERUSE, since it could interfere with your ability to run the program normally.
_PCHECK Command Process Definition Commands Figure 2-1. Examples of Using the DP Command 1> DP FUP /PNAME FU,MACRO VOLUMER/ ==define the first process pstart: starting \HOME.$SYSTEM.SYS01.FUP process 2> FU ==invoke the process VOLUME $DATA.MYSUBV -3-- INFO * ==issue a local FUP command CODE EOF LAST MODIF OWNER RWEP $DATA.
Process Definition Commands _PCHECK Command requested. The PINFO command, defined later, provides a subset of the information that _PCHECK provides. Note. If your TACL use list is not set up to include :utils:DP, you must precede the _PCHECK command with :utils:dp. _PCHECK [ / option [ , option ]... / ] [ process-list ] option is any of the following options: EXISTENCE returns -1 if the process is defined; otherwise, it returns 0.
_PCHECK Command Process Definition Commands PREPARSE returns the name of the preparser of the process, if defined. PROCESSID returns the operating system name of the process, if the process is running. PROGRAMFILE returns the file name of the program being executed. QUICK returns -1 if the process is restarted without waiting for the prompt; otherwise, it returns 0. QUIET returns -1 if the confirmation message is printed when starting the process; otherwise, it returns 0.
Process Definition Commands PHELP Command Considerations If you specify more than one request option, the pieces of information are separated by spaces and are listed in the same order as the requests. If you specify more than one process name, the groups of information for each process are separated by spaces and are listed in the same order as the requests. Information is returned for previously-defined processes.
PINFO Command Process Definition Commands PINFO Command Use the PINFO command to display the status and characteristics of one or more defined processes. Note. If your TACL use list is not set up to include :utils:DP, you must precede the PINFO command with :utils:dp. PINFO [ / DETAIL / ] [ process-list ] DETAIL gives detailed information on status and characteristics of the specified defined processes. See Figure 2-3 for the display format provided by the DETAIL option.
Process Definition Commands POUT Command Figure 2-3. PINFO Listing With Detail NAME PROGRAM PROCESS FILE INPUT OUTPUT READY FLUP P PS EDEDIT FUP PERUSE PSMAIL EDIT 2,82 6,24 7,104 \EASTUS.4,64 $F108.#S13 $F108.#S12 $F108.#S15 $F108.#S11 EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY YES YES YES YES WAIT HISTORY PROMPT YES YES YES YES YES YES YES YES NO NO NO NO In the READY column, YES is displayed if the process is running and ready to accept commands; if not, NO is displayed.
PSHOW Command Process Definition Commands Considerations If you press the BREAK key during output and the process is prompting, the portion of the output viewed since the process prompted is not removed from the output queue. PSHOW Command The PSHOW command displays accumulated output from a defined process or input that is yet to be sent to the process. The display can be sent to a specified file or variable instead of to your terminal.
Process Definition Commands PSTOP Command looking at the input to see how many commands are yet to be executed by the process, or by looking at the output to see how much output has been produced. PSTART Command The PSTART command starts a process if the process is not already running. If the process cannot be started, a message is displayed. Note. If your TACL use list is not set up to include :utils:DP, you must precede the PSTART command with :utils:dp.
TOSS Command Process Definition Commands Considerations • • You can use the PSTOP command if your current user ID is included for the permissions of this process. Removing a defined process automatically stops the process. TOSS Command The TOSS command deletes accumulated input or output from an input or output queue of the process. You can use TOSS to discard unwanted input or output after issuing a NOWAIT command or after pressing the BREAK key during output. Note.
Process Definition Commands WAIT Command process-list is a list of unique, symbolic names you have assigned to defined processes. If you specify an asterisk (*), information for all your defined processes is displayed. Considerations • • Once a process is undefined, all attributes of the process are lost. To restart the process, you must define it again using DP. UNDP issues the PSTOP command to stop a process.
WAITREADY Command Process Definition Commands WAITREADY Command The WAITREADY command simply waits for the specified process to prompt. Output from the process is preserved and not displayed. You can use WAITREADY after issuing a NOWAIT command to synchronize with the process. If you change your mind and want to return to the TACL prompt before the process prompts, press the BREAK key. Note. If your TACL use list is not set up to include :utils:DP, you must precede the WAITREADY command with :utils:dp.
Process Definition Commands Issuing Commands to a Defined Process IN file-name takes input from the specified existing file. INV variable takes input from the specified existing variable. out-option is any of the following options: OUT file-name waits for the process to finish and then directs its output to the named file. If the file does not exist, it is created. OUTV variable waits for the process to finish and then directs its output to the named existing variable.
Issuing Commands to a Defined Process Process Definition Commands To exit from passthrough mode and return to the TACL prompt, type CTRL-Y or BREAK. Considerations • • • • • • • 2- 20 The BREAK key is processed by TACL and cannot be passed to a defined process. If a process depends on the BREAK key to cancel processing, you can stop processing only by stopping the process. If a process produces output in which you are not interested, use the TOSS command to delete the output.
3 Using Define Process Commands Using Define Process Commands To use Define Process commands, the TACL process that you are using must be named. You can use the STATUS *,TERM command on the TACL screen to check whether your TACL process is named; if it is, you can proceed with these exercises. To use the Define Process commands from any TACL process, follow these steps: 1. Type the TACL command, DP, to put the Define Process directory in the TACL process #USELIST.
Using Remote Processes Using Define Process Commands The PERUSE process keeps running and remains ready for commands, as shown in the next step. f. Type > PINFO. Note that PERUSE is still ready. g. Type > FP to access your defined FUP process by using its logical name. The FUP prompt is a hyphen; thus two hyphens follow the history number. h. Type the FUP command INFO to list the files in your subvolume.
Using Define Process Commands Using Remote Processes This starts a remote TACL process named A on system node \REMO. 3. Type > A to go to the remote TACL. Note that the remote TACL has its own history number, that follows the local TACL history number. 4. Type > STATUS *,PROG $SYSTEM.SYSTEM.PATHMON From the information displayed, pick a valid PATHMON name (for example, $PTMI) for use in Step 7 and press [CTRL-Y]. 5. Return to your local TACL. 6.
Using Remote Processes Using Define Process Commands 3- 4 131360 —Define Process Manual
Glossary Introduction This glossary defines technical terms used in this manual. Some of these terms are also defined in the SPI Programming Manual. abend (abnormal end). (1) An abnormal end of a task or process. (2) An error condition that can result in the termination of a program. action event. An event for which the generating subsystem requires a response from the operator, such as mounting a tape.
clipboard file Glossary clipboard file. An EDIT file to which you can copy selected lines from a ViewPoint display screen. You, or a management application program, can then access the selected lines of text in that file at some later time. Copying to the clipboard file is called clipping. command. A demand for action by or information from a subsystem, or the operation demanded by an operator or application. A command is typically conveyed as an interprocess message from an application to a subsystem.
Glossary Extras application as the primary-events distributor, the alternate-events distributor, and the last-events distributor. DSM. See Distributed Systems Management. event. A significant change in some condition in the system or network. Events can be operational errors, notifications of limits exceeded, requests for action needed, and so on. Events are reported to ViewPoint as event messages to be displayed on a Primary Events, Alternate Events, or Last Events screen. event cache.
filter Glossary filter. A file that contains a list of criteria against which incoming event messages can be compared so as to pass a given message (if it meets all criteria) or not pass it (if it fails one or more criteria). filter object file. A file containing the compiled filter code that determines which events are displayed on an events screen. high PIN (process identification number). A PIN that is greater than 255. See also low PIN. historical mode.
Glossary programmatic interface Network Status Summary screen. The screen on which ViewPoint displays information about the status of objects in a network. object. In SPI, an entity subject to independent reference and control by a subsystem: for example, the disk file $DATA or the data-communications line $X2502. An object typically has a name and a type known to the controlling subsystem. There might also be aliases for the name and type in the DNS database. In DDL, an item in a dictionary.
programmed operator Glossary the requester and the server; and software to receive and respond to messages defined for the interface. programmed operator. A management application that performs functions that might otherwise be performed by a human operator. reply, reply message. One message from a server to a requester, in reaction to a request. request, request message. One message from a requester to a server. response. The information or confirmation supplied by a subsystem in reaction to a command.
Glossary token Status Configuration screen. The ViewPoint screen on which the operator can specify configuration information to control the display of status items on the Network Status Summary screen. status item. A measurable condition in a system or network that is displayed on one line of a Network Status Summary display screen. Each such item is separately chosen and configured for display by use of the Status Item Configuration screen. Status Item Configuration screen.
token code Glossary response, or control information for SPI or the subsystem. For event management, a token normally represents an item of information about an event, or control information for EMS or the subsystem. token code. In SPI, a 32-bit number, or the variable name representing that number, that consists of a token type and a token number.
Index B Background process 2-2 BLANK key word 2-18 BREAK key, used with defined process 2-13, 2-20, 3-1 C CPU key word 2-2 CTRL-Y, used with defined process 2-8, 3-3 D DCT See Destination control table DEBUG key word 2-3 DEFAULTS Define Process commands list of 2-2 directory 2-2, 2-16 library overview 1-1 Define Process command definition 2-2 Define Process library 3-1 Defined process current userid 2-15 default symbolic name 2-7 discarding input-output 2-16 echoing of prompt 2-6 examples 2-7 GUARDIAN 90
H Index H O Help for Define Process commands 2-11 HISTORY key word, _PCHECK 2-9 History number 2-19 in defined process 3-1 History processing, enable/disable 2-4 Home terminal for defined process 2-6 OUT key word 2-13, 2-14, 2-17, 2-19 Out queue 2-14, 3-1 OUTPUT key word 2-14, 2-16 Output queue 2-14, 3-1 OUTPUTLINES key word, _PCHECK 2-9 OUTPUTV key word, _PCHECK 2-9 OUTV key word 2-13, 2-14, 2-17, 2-19 I IN key word 2-19 In queue 2-14, 3-1 INPUT key word 2-14, 2-16 Input queue 2-14, 3-1 INPUTLINES ke
Index Pstart message 3-1 PSTART command definition 2-15 PSTOP command definition 2-15 Q QUICK key word 2-5 _PCHECK 2-10 QUIET key word 2-6 _PCHECK 2-10 R READY key word, _PCHECK 2-10 Remote defined process 3-2 Remote password 2-1 RUNNING key word, _PCHECK 2-10 RUNOPTS key word, _PCHECK 2-10 S Special Characters U Undefining a defined process 2-16 UNDP command definition 2-16 using 3-1 USE DP command 3-1 UTILS DP directory 3-1 W WAIT command definition 2-17 WAIT key word 2-19 _PCHECK 2-10 Wait mode 2-
Special Characters Index- 4 Index 131360 —Define Process Manual
