Commands ABORT to BYE

None.

The ABORT command terminates a process that has been suspended by pressing the Break key. Programs do not terminate while critical system code is executing on their behalf, but terminate immediately following execution of that code.

The ABORT command is available only from a session and only during BREAK, but it does not disrupt the session. Some operations abort immediately upon entering BREAK without requiring the ABORT command. An ABORT command results in the job control word (JCW) being set to the SYSTEM 0 state. For a discussion of job control words, refer to the SETJCW command.

This command may be issued from a session (in BREAK only). It is not available from a job or a program. Pressing Break has no effect on this command.

To abort the current program or operation, press Break. When the colon prompt (:) appears, enter:

  ABORT

The system then displays the message PROGRAM ABORTED PER USER REQUEST and redisplays the colon prompt (:).

This command aborts a single pending I/O request for the specified ldev. To delete all queued I/O requests for a device, repeat the ABORTIO command until the following message appears on the $STDLIST device:

  NO I/O TO ABORT FOR DEVICE #ldev

Devices that are job-accepting or data-accepting always have outstanding READ requests pending, due to the auto-recognition feature of MPE/iX. Use the ABORTIO command to clear these pending input requests.

Sometimes, you may need to clear all outstanding I/O requests to allow proper execution of other console commands including ABORTJOB, TAKE, DOWN, and REFUSE.

	NOTE: If the ABORTIO command is not effective from the system console, use the =ABORTIO command. (You can only issue the CTRL A =ABORTIO command from the physical console.) Use the =ABORTIO command only when you cannot execute the ABORTIO command.

You may issue the ABORTIO command from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It is executable only from the console unless distributed to users with the ALLOW or ASSOCIATE command.

The =ABORTIO console command cannot be issued from a job.

To abort a pending I/O request for logical device 53, enter:

  ABORTIO 53

It is necessary to issue several ABORTIO commands to abort all pending I/O operations on a spooled device, as shown below:

  STOPSPOOL 5
  11:20/31/SP#5/STOPPED
  11:20/31/LDEV#5 NOT READY
  REFUSE 5
  ABORTIO 5
  ABORTIO 5
  11:21/40/NO I/O TO ABORT FOR DEVICE 5

The ABORTJOB command terminates the designated job or session, and displays the following message on the job/session list device:

  SESSION ABORTED BY SYSTEM MANAGEMENT

If you use the [jobname,]user.acct form of the command when there is more than one job or session executing under that name, MPE/iX selects which job/session to abort. Therefore, to exercise more precise control when aborting jobs or sessions, use the #Jnnn or #Snnn form of the ABORTJOB command. Although the job/session is abnormally terminated, log records are issued, and CPU-times and connect-times are updated. Any I/O activity, such as printing or file storage, is terminated.

The ABORTJOB command can be applied to waiting and scheduled jobs, as well as to executing jobs. If the spooler input file ($STDIN) for a batch job has been created and not yet opened (in other words, the job is in the WAIT state), the entire file is deleted. If the ABORTJOB command is issued before the output spoolfile is complete, only that portion of the file already spooled is printed, along with an error message indicating that the job was aborted. If a request is pending at the system console, it is automatically terminated by the ABORTJOB/=ABORTJOB command and the following message appears on the system console:

 time/#Snnn/pin/REQUEST REQUIRING OPERATOR REPLY FOR PIN #nn HAS BEEN ABORTED

When the ABORTJOB command is successful, a logoff message is displayed on the console, indicating that the job has been aborted, as shown in the example below:

  ABORTJOB #S9
  11:20/#S9/34/LOGOFF ON LDEV #77

The standard error message that appears when a request is manually terminated by entering Y in response to =REPLY (or REPLY) is displayed on the user's terminal:

  SESSION ABORTED BY SYSTEM MANAGEMENT

The =ABORTJOB command may be used at the physical console if ABORTJOB is ineffective. Refer to the "Use" section of this command.

You may issue this command from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It is executable only from the console unless it is distributed to users with the ALLOW command, or the JOBSECURITY command is set to LOW with AM or SM capability.

=ABORTJOB may be issued only from the console.

	NOTE: Users with AM capability may only abort jobs and sessions within their own account. Users with SM capability may abort jobs and sessions across accounts.

To terminate session number 139, enter:

  ABORTJOB #S139
  17:10/#S139/34/LOGOFF ON LDEV #62

To terminate job number 9, enter:

  ABORTJOB #J9
  20:18/#J9/26/LOGOFF ON LDEV #10

In both of the preceding examples, the LOGOFF ON LDEV # messages indicates that ABORTJOB command was successfully executed.

To terminate session 6, which has a pending device allocation message, enter:

  ?17:00/#S6/23/LDEV# FOR "SCRTAPE" ON TAPE (NUM)?
  ABORTJOB #S6
  17:10/#S6/120/REQUEST REQUIRING OPERATOR REPLY FOR
  PIN 23 HAS BEEN ABORTED
  17:10/#S6/120/LOGOFF ON LDEV #58

ABORTPROC [ [PIN=]{pinspec }]

{(pinspec [,pinspec ]...)}

[;SYSTEM]

The ABORTPROC command attempts to abort the specified process(es) and all of their children processes. MPE/iX currently does not support a means for children processes to survive the death of their parent process. If one or more child processes cannot be aborted, their parent process cannot be terminated either.There are specific circumstance where a process is not abortable. Examples discussed below involve "critical" processes and session processes in break mode.

The MPE/iX Operating System uses a mechanism known as SETCRITICAL to prevent a process from being aborted. The SETCRICIAL method is used to protect the integrity of system data structures. A process that is SETCRITICAL cannot be aborted. It is normal for all processes to periodically be SETCRICIAL (e.g., when executing system code), and they will RESETCRITICAL when it is safe for them to be aborted. The ABORTPROC command works in conjunction with the SETCRITICAL mechanism. It is designed so that it will never abort a process which is SETCRICIAL. If a process is critical, ABORTPROC will notify the process that it should abort as soon as it is possible to terminate safely.

If the target process, or any of its children processes, are in break mode they cannot be aborted, and an error is reported. This is due to the MPE implementation of break, and because all processes in the same session process tree share the same terminal LDEV. The target process needs to be resumed before it can be aborted by the ABORTPROC command. The one exception is when the target process is the usermain process, typically the CI. In this case it is abortable by ABORTPROC, even when it is in break mode.

When ABORTPROC fails to fully terminate the process the target process is marked as having an "abort pending". Processes with aborts pending are terminated when the condition that prevented the successful abort is resolved. When ABORTPROC is used on a process that is already marked as dying, a CI warning is reported.

System supervisor (OP) or System Manager (SM) capability is required to execute the ABORTPROC command. SM capability is necessary to abort detached system processes.

The ABORTPROC command may be issued from a session, job, program, or in BREAK. Pressing [Break] aborts the execution of this command.

	NOTE: Users with AM capability may only abort jobs and sessions within their own account. Users with SM capability may abort jobs and sessions across accounts.

To abort process 133 and its current descendants, enter:

ABORTPROC #P133 or
ABORTPROC 133

To abort processes 122, 133 and 175, enter:

ABORTPROC (122, 133, 175)

	NOTE: To specify a list of processes, enclose the list inparenthesis and separate the pinspecs with commas.

To abort process 85 (assuming PIN 85 is a detached system process), enter:

ABORTPROC 85;SYSTEM

	NOTE: SM capability is required to abort system processes.

The operator or system supervisor uses this command to designate which devices may be used to initiate jobs or sessions and/or data. When a device is configured as an accepting device, MPE/iX automatically scans the first input record for a valid JOB, HELLO, or DATA command. This feature, called auto-recognition, allows users to access the device without specifically requesting use of the device with a message to the system console.

If you explicitly specify the JOBS parameter, the ACCEPT command is not executed unless the device is configured as a default output device.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It is executable only from the console unless distributed to users with the ALLOW command.

To permit logical device 19 to accept jobs and data, enter:

  ACCEPT 19
  SHOWDEV 19
 
  LDEV AVAIL  OWNERSHIP  VOLID ASSOCIATION
   19 AVAIL

To permit logical device 19 to accept jobs and data, and to allow the device to be spooled, enter:

  ACCEPT 19
  STARTSPOOL 19
  11:12/31/SP#/SPOOLED IN
  11:12/6/LDEV#19 NOT READY
  SHOWDEV 19
 
  DEV AVAIL  OWNERSHIP VOLID DEN ASSOCIATION
  19 SPOOLED SPOOLER OUT

A program or procedure is allocated by resolving external references and assigning code segment table (CST) or extended code segment table (XCST) entries to the program's code segments. Table entries are also allocated for any procedures called by the allocated program or procedure. Allocating a program or procedure does not increase execution speed but it does reduce the time it takes to load the program for execution.

	CAUTION: Use care in deciding which programs or procedures to load with the ALLOCATE command. The number of CST table entries is limited and, if the limit is exceeded, data may be lost.

Segments remain loaded until they are deallocated with the DEALLOCATE command, or until the system is shut down or a system failure occurs. Programs or procedures must be reallocated with the ALLOCATE command following any start up.

To issue the ALLOCATE command a user must have EXECUTE access for any file referenced in the name parameter of this command.

Any external procedures referenced by a program being allocated by this command must reside in SL.PUB.SYS.

	NOTE: Native mode (NM) and Compatibility Mode (CM) loader error messages are reported differently, allowing you to determine the system in which the error occurred. NM Loader Error: ErrMessage (LDRERRnnnn) CM Loader Error: ErrMessage (LOAD ERRnnnn)

This command may be issued from a session or program. Pressing Break has no effect on this command. System supervisor (OP) capability is required to use this command.

In addition to comma (,) a semicolon (;) and equal sign (=) may be used as a delimiter.

To allocate a procedure identified as PROC1, that resides in SL.PUB.SYS, enter:

  ALLOCATE PROCEDURE,PROC1

Program files residing in the nonsystem domain (a volume set) are not allocated. Attempts to do so result in a LOAD ERR 92 message.

The operator uses the ALLOW command to distribute specific operator commands to system users. ALLOW specifies which users may execute operator commands, and which commands they may execute.

You may specify an indirect file with the ALLOW command, or you may execute ALLOW in subsystem mode. Each of these is explained below.

Using an indirect file to allow commands

To allow commands via an indirect file, you create a file that contains records identifying the users and accounts to whom you are allowing operator commands, followed by the list of commands allowed.

Using an indirect file with the ALLOW command is particularly convenient for system administrators since, once you make the file, you can reuse it to disallow the set of commands (via the DISALLOW command) or to allow the same set of commands again.

Here is an example of an indirect file:

  EDITOR
  HP32201A.07.17 EDIT/3000 TUES, MAY 29, 1994, 5:08 PM
  (C) HEWLETT-PACKARD CO. 1985
  /ADD
  1  SUSAN.PAYROLL;COMMANDS=ALTJOB,ALTSPOOLFILE
  2  JOHN.ACCTNG;COMMANDS=ALTJOB,DELETESPOOLFILE
  3  //
  ...
  /KEEP ALLOWTMP
  /E

Once you create an indirect file, you then issue the ALLOW command, using the ;SHOW parameter to display each command line as it is executed from the file. For example:

  ALLOW FILE=ALLOWTMP;SHOW

You may backreference the file with a file equation as follows:

  FILE BACKF=ALLOWTMP
  ALLOW FILE=*BACKF;SHOW

If the file has a lockword, enter it in the command line after the filename. For example, "ALLOWTMP/password".

Using ALLOW in subsystem mode

To use the ALLOW command in subsystem mode, following these steps:

You cannot use the FILE= parameter in subsystem mode. The ALLOW subsystem will terminate if it encounters an error.

You may allow commands only to users who are currently logged on unless you specify the @.@ option, which allows commands to all users. (Since this option has obvious disadvantages, you can remedy the situation by then issuing a DISALLOW command to disallow command use to selected users.)

Additional capabilities granted to a user are valid only for the duration of their current session. Once the user logs off, any special capabilities previously assigned are no longer applicable.

To determine which operator commands have been allowed globally (that is, using the @.@ construct), or to a specific user, use the SHOWALLOW command.

	NOTE: Do not confuse console commands which are NOT allowable with operator commands. Operator commands are used in the day-to-day operation of your system and are generally allowable. A console command must be executed on the actual system console and must be preceded by cntl-A. Some console commands have the same name as non-console commands, an example is RECALL, which may be executed on any device.

The following is a list of commands that may be allowed.

  ABORTIO     HEADON       RESUMESPOOL
  ABORTJOB    JOBFENCE     SHUTQ
  ACCEPT      JOBSECURITY  STARTSPOOL
  ALLOW            LDISMOUNT    STOPSPOOL
  ALTJOB           LIMIT        STREAMS
  ALTSPOOLFILE     LOG          UP
  CONSOLE          MRJECONTROL  VMOUNT
  DELETESPOOLFILE  OPENQ        VSCLOSE
  DISALLOW         OUTFENCE     VSOPEN 
  DISCRPS          REFUSE       VSRELEASESYS
  DOWN             REPLY        VSRESERVESYS
  DOWNLOAD         RESUMEJOB    WARN
  HEADOFF         SPOOLER     WELCOME

You may issue this command from a session, job, program, or in BREAK. Pressing Break will terminate subsystem mode and produce an error message but has no effect on commands already entered in subsystem mode. This command is executable only from the console unless distributed to users with the ALLOW command.

To give the user USER.TECH the ability to execute the REPLY and ABORTIO commands, you would enter the following at the system console:

  ALLOW USER.TECH;COMMANDS=REPLY,ABORTIO

In subsystem mode, to give the user MGR.MANUALS the ability to execute the BREAKJOB command, you would enter the following at the system console:

  ALLOW
  >MGR.MANUALS;COMMANDS=BREAKJOB
  >EXIT

ALTACCT acctname [ ;PASS=[ password] ] [ ;FILES=[ filespace]] [ ;CPU=[ cpu]] 

[ ;CONNECT=[ connect] ] [ ;CAP=[ capabilitylist] ] [ ;ACCESS=[ (fileaccess)]] 

[ ;MAXPRI=[ subqueuename] ] [ ;LOCATTR=[ localattribute] ] 

[ ;ONVS=volumesetname] [ ;USERPASS=[ {REQ | OPT } ] ] (1)

(1) The USERPASS parameter is only available if the HP Security Monitor has been installed.

The system manager uses the ALTACCT command to change the attributes of an existing account. You may enter multiple keywords on a single command line as shown in "Examples." When you change one capability in a capabilitylist that contains several nondefault values, you must specify the entire new %capabilitylist. When you omit an entire keyword parameter group from the ALTACCT command, that parameter remains unchanged for the account. When you include a keyword, but omit the corresponding parameter (for example, PASS= Return), the default value is assigned. Table 2-2 lists the default values for the ALTACCT command.

Table 3-1 “Default Parameters for the ALTACCT Command” shows the defalut parameters for the ALTACCT Command.

Any value changed with the ALTACCT command takes effect the next time MPE/iX is requested to check the value. If an attribute is removed from an account while users are logged on, they are not affected until they log off their current job or session and log on again. MPE/iX does not automatically generate a message informing users of the change; it is your responsibility to warn account members in advance of any changes. If you take a capability away from an account, all account members and groups within the account are denied the capability the next time that they log onto the account.

You cannot remove system manager (SM) capability from the SYS account or account manager (AM) capability from any account. From within any account, you can remove AM capability from all but one (the last) of the users assigned it. It is possible, however, to remove AM capability from all users in an account, but only if you do so from another account that has SM capability.

	NOTE: If you specify volume-related commands or parameters for a volume set that is not currently mounted, or for an account that does not exist, MPE/iX returns an error message.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. System manager (SM) capability is required to use this command.

To change an account named AC2 so that its password is GLOBALX, and its filespace is limited to 50,000 sectors, enter:

  ALTACCT AC2;PASS=GLOBALX;FILES=50000

To change the password and the file space of an account called MALCHIOR in the volume set TIME_LORD, you need to issue two commands:

  ALTACCT MALCHIOR;PASS=OMSBOROS
  ALTACCT MALCHIOR;ONVS=TIME_LORD;FILES=20000

You must specify the changes for the system volume set (the first command) and for the volume set itself (the second command). Specifying a volumesetname limits the user to changing only FILES in the second command.

You use the ALTFILE command to alter a file's characteristics. Currently the attributes that you may modify are the owner (UID) and POSIX group (GID) for a file, hierarchical directory, MPE group or account, with the restriction that you may not alter the GID for MPE groups or accounts.

You must have the appropriate privilege to change the requested attribute(s). In order to change the UID of a file, you must be one of the following:

In order to change the GID of a file, you must be one of the following:

You may issue the command once to modify multiple attributes. If you specify multiple attributes, all modifications must succeed for any to take effect. If you enter no attributes, the command has no effect on the specified file.

This command changes one or more attributes of a group. Multiple parameters may be specified on a single command line as shown in "Examples." When an entire parameter is omitted from an ALTGROUP command, the corresponding value for the group remains unchanged. When a keyword is included but the corresponding parameter is omitted (as in PASS = Return), the default value is assigned. Table 2-3 lists the default values for the ALTGROUP command. Table 3-2 “Default Values for the ALTGROUP Command” shows the default values for the ALTGROUP Command.

When a parameter is modified with the ALTGROUP command, it immediately takes effect in the directory. It does not affect any active users with open files in the group, until they log off their current session and log on to that username and group again. For this reason, notify all group users of any planned changes in advance.

	NOTE: If you specify volume created commands or parameters for a volume set that is not currently mounted, or for an account that does not exist, MPE/iX returns an error message.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. Account manager (AM) or system manager (SM) capability is required to use this command.

To assign a new password, PASS2, to a group named GROUPX, enter:

  ALTGROUP GROUPX;PASS=PASS2

To alter the group LEILA that resides on the volume set TIME_LORD:

  ALTGROUP LEILA;ONVS=TIME_LORD;FILES=10000

If the group LEILA contains no files, and no one is logged onto the group, you may also alter the home volume set to DICHONDRITE, provided DICHONDRITE exists and is recognized by the system:

  ALTGROUP LEILA;HOMEVS=DICHONDRITE

However, if LEILA does contain files, you cannot change the home volume set for this group without creating a new group and transferring those files to it.

The ALTJOB command, in conjunction with the JOBFENCE command, allows you to control the flow of all jobs on the system with the exception of HIPRI jobs. It can be used to alter only jobs in the INTRO, WAIT, or SCHED state. Jobs with an input priority less than or equal to the current JOBFENCE, a numerical value from 0 to 14, are deferred.

This command may be issued from a session, job, program, or in BREAK. Pressing BREAK has no effect on this command. If issued from the console or by a user with SM capability, or allowed via the ALLOW command, the ALTJOB command can be used to alter any job. A user who is not at the console, does not have SM or has not been allowed the command may issue ALTJOB only if jobsecurity is set to low. If jobsecurity is set to low then all users can issue ALTJOB against their own jobs and account managers (AM capability) can issue it against any job in that account.

In the following example, three jobs are submitted by users, each with an INPRI value of 8. To change the INPRI values to ensure that JOB1 runs first, JOB2 runs last, and JOB3 runs second with LP allocated as the OUTDEV for JOB3, enter the following commands:

  JOBFENCE 14
  15:11/#J1/24/DEFERRED JOB INTRODUCED ON LDEV #53 
  15:11/#J2/25/DEFERRED JOB INTRODUCED ON LDEV #53 
  15:13/#J3/26/DEFERRED JOB INTRODUCED ON LDEV #53 

  SHOWJOB
 
  JOBNUM  STATE IPRI JIN  JLIST INTRODUCED JOB NAME
 
  #S23   EXEC     20  20   THU 2:15P OPERATOR.SYS
  #J1   WAIT  D 8  10S 12   THU 3:11P JOB2,OP.SYS
  #J2   WAIT  D 8  10S 12   THU 3:11P JOB3,SUE.PAYROLL
  #J3   WAIT  D 8  10S 12   THU 3:13P JOB1,JIM.ACCTG
 
  4 JOBS:
   0 INTRO
   3 WAIT; INCL 3 DEFERRED
   1 EXEC; INCL 1 SESSIONS
   0 SUSP
  JOBFENCE= 14; JLIMIT= 5; SLIMIT= 16
 
  ALTJOB #J1;INPRI=10
  ALTJOB #J3;INPRI=9;OUTDEV=LP
  ALTJOB #J2;INPRI=8
  JOBFENCE 6
  SHOWJOB

  JOBNUM  STATE IPRI JIN  JLIST INTRODUCED JOB NAME
 
  #S23   EXEC     20  20   THU 2:15P OPERATOR.SYS
  #J1   EXEC   10  10S 12   THU 3:13P JOB2, OP.SYS
  #J3   EXEC   9  10S LP   THU 3:11P JOB1,JIM.ACCTG
  #J2   EXEC   8  10S 12   THU 3:11P JOB3,SUE.PAYROLL
 
  4 JOBS:
   0 INTRO
   0 WAIT; INCL 0 DEFERRED
   4 EXEC; INCL 1 SESSIONS
   0 SUSP
  JOBFENCE= 6; JLIMIT= 5; SLIMIT= 16

This command changes the attributes of an existing user logging identifier to those specified in the parameter list. Parameters not included in the ALTLOG command retain their current values. System supervisor (OP) or user logging (LG) capability is required to use this command. Only the creator of the logging identifier can alter its attributes.

To use the AUTO parameter, the log process for logid must be enabled for changing. You may do this by ending the log file name with the numeric characters 001 (for example, fname001). This naming convention works in conjunction with the file set number to generate sequential file names automatically.

If a log file is restricted to a single volume or volume class when it is created with the BUILD command, then successive log files created by User Logging will have the same restriction.

If a new log file name is specified with the ALTLOG command, the links with any previous log file are broken.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. User logging (LG) capability is required to use this command.

To change the destination log file of the logging identifier KIM to log file C and specify that C resides on disk, enter:

  ALTLOG KIM;LOG=C,DISC

Since the keyword parameter, PASS=, was omitted, KIM retains any password previously specified.

To execute the ALTPROC command, you must have System Supervisor (OP) or System Manager (SM) capability. SM capability is necessary to alter system processes, for the WG= option, for certain specifications to the PRI option, and to increase a process' priority above MAXPRI. You may issue the ALTPROC command from a session, job, program, or while in BREAK. Pressing Break aborts the execution of this command.

To alter process 605, and its current descendants, so that their priorities execute within the DS_Default workgroup, enter:

  :ALTPROC #p605; tree; wg=DS_Default

To alter process 605, and its current descendants, so that their scheduling queue attribute is DS, enter:

  :ALTPROC #p605; tree; pri=DS

The outcome of this command is not necessarily identical to the outcome achieved with the previous command. If the system was configured with a user-defined workgroup that captured the processes (MEMB_QUEUE=DS and a match on other membership attributes, if specified), then the processes would be a member of the user-defined workgroup rather than the DS_Default workgroup.

To alter all job processes to the CS_Default workgroup, enter:

  :ALTPROC job=@j; wg=CS_Default; anyuser

To return the processes modified by the previous example to their natural workgroup(s), enter:

  :ALTPROC job=@j; wg=NATURAL_WG; anyuser

To alter all job processes matching the user's name to the CS_Default workgroup, enter:

  :ALTPROC job=@j; wg=CS_Default; user

To alter the current process' priority so that it behaves like a CS queue manager (SM capability required), enter:

  :ALTPROC 0;pri=CM

To alter all processes logged on as mgr.payroll to linear 155 (SM capability required), enter:

  :ALTPROC job=mgr.payroll; pri=155

To alter the queue attribute of pins 150, 247, 211 to be ES, enter:

  :ALTPROC (150,#p247,211); pri=ES

You use the ALTSEC command to alter security provisions for files, hierarchical directories, devices, and device classes by manipulating an object's access control definition (ACD) or its access mask. All of these objects may have ACDs, but only files have access masks which can be changed using this command. An object's ACD may be altered using this command with the ACD keywords NEWACD, REPACD, COPYACD, ADDPAIR, REPPAIR, DELPAIR, DELACD, and MASK.

A file's access mask may be altered using either the ACCESS keyword or an access specification without a keyword. Using the ACCESS keyword is a recommended practice to help distinguish between file access mask and ACD operations. Only the owner of a file can use the ALTSEC command to change a file's access mask. Object owners and users with appropriate privilege can use this command to manipulate an object's ACD. Files and hierarchical directories have their owner's identity and a file group ID (GID) stored in their file labels. System managers have the appropriate privilege to manipulate the ACDs for all objects. Account managers for the account matching an object's GID have appropriate privilege. Devices are owned by system managers. The ability to manipulate an ACD or file mask is not affected by the object access currently granted to a user.

File ACDs override file lockwords and the file access matrix. ACDs permit more precise access control than the file access matrix by allowing access permissions to specific users. MPE/iX allows you to specify a maximum of 40 ACD pairs for a particular object. Since a large number of ACD pair specifications overflows the command line buffer, you must enter large numbers of ACD specifications may be entered through an indirect file.

The ALTSEC command fails if you attempt to alter the access permissions for a permanent disk file whose group's home volume set is not mounted.

Release 5.0 requires ACDs on the following files:

Required ACDs cannot be removed with the ALTSEC command even by users with SM or AM capability.

To view the file access matrix, use LISTFILE,4.

You have created a file named FDATA, and want to change its file access matrix access permissions to grant write access to only yourself. Enter:

  ALTSEC FDATA;ACCESS=(W:CR)

To change file access permissions for the FPROG program file to allow all group users to execute programs, but only account and group librarian users to read or write to the file, enter:

  ALTSEC FPROG;ACCESS=(X:GU;R,W:AL,GL)

To view ACD information, use the LISTFILE,-2 command. This form of the LISTFILE command displays only ACD information.

You have created a file named FDATA, and want to assign a new ACD to FDATA, granting write access to a user named FRIEND.ACCT. Enter:

  ALTSEC FDATA;NEWACD=(W:FRIEND.ACCT)

As the creator of a file, you can access the file by default, so you don't need to grant yourself access through an ACD. Users with appropriate privileges are always permitted to access files protected by ACDs.

To extend the ACD for the FDATA file so that all users on the system can read it, and all users within your account ACCT can also write to it, enter:

  ALTSEC FDATA;ADDPAIR=(R:@.@;W,R:@.ACCT)

If you decide that users outside your account ACCT should not have read access to the file FDATA any longer, enter:

  ALTSEC FDATA;DELPAIR=(@.@)

This does not delete all ACD pairs, only the ACD pair matching @.@. To delete the entire ACD, enter:

  ALTSEC FDATA;DELACD

To replace the entire ACD, enter:

  ALTSEC FDATA;REPACD=(W:FRIEND.ACCT)

You want to copy the ACD associated with LDEV 5 to all devices in device class TERM:

  ALTSEC TERM,DEVCLASS;COPYACD=5,LDEV

ACDs may be copied only between objects of the same type.

You want to grant users in account ACCT all access to directory Mydir1:

  ALTSEC ./Mydir1;ADDPAIR=(CD,DD,RD,TD,RACD:@.ACCT)

You want to grant read and write access to yourself and read access for other members of your group to an HFS Syntax file named a_file_of_Mine:

  ALTSEC ./a_file_of_Mine;REPPAIR=(RACD,R,W:$OWNER;
  RACD,R:$GROUP,$GROUP_MASK;NONE:@.@)

To add a new ACD to file PROGNAME allowing all users on the system to execute it, but only users in account ACCT to write to it enter:

  ALTSEC PROGNAME;NEWACD=(X:@.@;W,X:@.ACCT)

To add a new ACD pair to an ACD which already exists for file PROGNAME which will allow the user ENGR of the LAB account to read, write, lock, append, execute and read the ACD information enter:

  ALTSEC PROGNAME;ADDPAIR=(R,W,X,RACD:ENGR.LAB)

Note that L and A (lock and append) need not be specified because they are implied with W (write).

To add an ACD that prevents any user except OPERATOR.SYS (and any user with SM capability) from accessing LDEV 7 (a tape drive), enter:

  ALTSEC 7,LDEV;NEWACD=(R,W:OPERATOR.SYS)

Note in the last example that X is not used because it makes no sense to execute a tape drive. It also makes no sense to lock or append a tape drive but W tacitly provides L and A anyway.

To eliminate any ACD that may be in effect for device class LP, and to prevent any user except MGR.FINANCE from writing to a printer in device class LP, enter:

  ALTSEC LP,DEVCLASS;DELACD
  ALTSEC LP,DEVCLASS;NEWACD=(W:MGR.FINANCE)

The operator uses the ALTSPOOLFILE command to change the printing priority of a spoolfile, to increase or decrease the number of copies produced, and/or to change the destination device or class.

When altering an ACTIVE spoolfile, first take the output device offline. This gives you time to enter the command and determine that the ACTIVE spoolfile is the file being printed. When the ALTSPOOLFILE command has been sent to the spooler process, MPE/iX returns the colon prompt (:). No change to the spoolfile is made, however, until the output device is returned online.

	NOTE: If you are altering the PRI or COPIES parameter for an ACTIVE spoolfile there is no need to take the output device offline. These two parameters can be altered while the device is online.

You may alter the outputpriority or the numcopies of an ACTIVE spoolfile without interrupting the printing process. If you alter the device or defer the ACTIVE spoolfile with the DEFER parameter, the printer stops immediately. In both cases, the entire file is printed when printing resumes. Deferring a spoolfile lowers its output priority to zero, the lowest priority possible. To print a deferred spoolfile, you must raise its priority above the current outfence using the ALTSPOOLFILE command.

If you intend to print a spoolfile on an HP 2680A Laser Page Printer, you may add an environment file to it before printing.

This command may be issued from a session, job, program, or in BREAK. Pressing Break has no effect on this command. It is executable from the console by users with system supervisor (OP) or system manager (SM) capability. It may be distributed to other users with the ALLOW or ASSOCIATE command.

To defer the ACTIVE spoolfile (#O86) on LDEV 6 take device 6 offline, then enter:

  ALTSPOOLFILE #O86;DEFER

or

  ALTSPOOLFILE 6;DEFER

To change the priority of deferred spoolfile #O123 from 0 to 3 enter:

  ALTSPOOLFILE #O123;PRI=3

ALTUSER username[ .acctname] 

[ ;PASS=[ password] ] [ ;CAP=[ capabilitylist] ] 

[ ; MAXPRI=[ subsueuename] ] [ ;LOCATTR=[ localattribut] ] 

[ ;HOME=[ homegroupname] ] [ ;UID=[ uid] 

[ ;USERPASS=[ req  opt ] [ Expired] ]

The USERPASS parameter is only available if the HP Security Monitor has been installed.

The ALTUSER command allows the account manager to change the password, capabilities, processing subqueue, security checking, and home group currently defined for a user. More than one of these attributes may be changed at a time, by entering multiple keyword parameters on a single command line, using the semicolon (;) delimiter.

To change an attribute, enter the keyword and its new value. When an entire keyword parameter group is omitted from the ALTUSER command, the corresponding value for the user remains unchanged. When a keyword is included, but the corresponding parameter is omitted (as in PASS=Return), a default value is assigned as shown in Table 3-3 “Default Values for the ALTUSER Command”.

When a parameter is modified with the ALTUSER command, it is immediately registered in the directory. However, it does not affect users who are currently logged on to the system. They are affected the next time they log on to the same user name and account. For this reason, warn users in advance of any intended changes.

Avoid changing the capabilitylist or homegroupname of the user MANAGER.SYS. SM capability cannot be taken away from MANAGER.SYS.

ALTUSER will not allow a user with AM capability to remove AM from their own capability list. However, a user with AM can remove AM from the capability list of another AM user inside the same account.

This command may be issued from a session, a job, a program, or in break mode. Pressing Break has no effect on this command. Account manager (AM) capability is required to use this command. System manager (SM) capability is required to specify a user in an account other than your own.

Suppose an account's capabilities are AM, AL, GL, SF, ND, PH, DS, MR, IA, and BA. To change the capabilitylist of the user JONES from IA, BA, SF, PH, DS to include multiple RIN (MR) capability, enter:

  ALTUSER JONES;CAP=IA,BA,SF,PH,DS,MR

To alter two attributes, password and subqueuename, for user JONES enter:

  ALTUSER JONES;PASS=JJ;MAXPRI=DS

This command links a device class, such as LP, to an individual user on the system. The user may then execute any valid operator command for a device in the device class and receive the status messages for the devices in that device class on $STDLIST. For example, a remote printer may be associated with a terminal, so that messages concerning the printer go to the terminal, not the system console.

Before a user can be associated, the system manager must run a utility program (the version of ASOCTBL.PUB.SYS that matches your operating system) in order to create a device class/user association table. This table defines which users may be associated with which device classes. At any given time, only one user may be associated with a given device class. If the device belongs in several device classes, only one of those device classes may be associated.

The operator commands, which may be made available to users through the ASSOCIATE command, are:

  ABORTIO           OUTFENCE
  ACCEPT           REFUSE
  ALTSPOOLFILE        REPLY
  DELETESPOOLFILE       RESUMESPOOL
  DISCRPS           SHUTQ
  DOWN            SPOOLER  
  DOWNLOAD          STARTSPOOL
  FORMSALIGN         STOPSPOOL
  HEADOFF           SUSPENDSPOOL
  HEADON           UP
  OPENQ

Both the system supervisor and the user may DISASSOCIATE a user from a device. In addition, a user implicitly disassociates a device when logging off.

This command may be issued from a session, program, or in BREAK. It may not be used from a job. Pressing Break has no effect on this command.

To be the controller of the device class TAPE, enter:

  ASSOCIATE TAPE

The BASIC command is generally used for online programming in BASIC/V, but it can also be used to interpret BASIC/V programs submitted in batch mode. In batch mode, the BASIC/V >EOD command is required after any data following the BASIC/V >RUN command, or after the >RUN command itself if there is no data.

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To enter commands and data from your standard input device, with program listing and output transmitted to the standard output device, enter:

  BASIC

You may also submit commands and data to the BASIC/V interpreter through input files that you have stored on disk. Files created using the editor must be kept with the UNN (unnumbered) option of the editor KEEP command. In this example, BASIC/V interpreter commands and statements are submitted from the command file MYCOMDS. The data that the program uses is stored in the input file MYDATA. The program listing and output are written to the file MYLIST.

  BASIC MYCOMDS,MYDATA,MYLIST

This command compiles, prepares, and executes a compatibility mode program from a "fastsave" file created by the BASIC/V interpreter. This enables the program to run faster than it would if it were executed by the interpreter.

To save the program after it is written, use the BASIC/V interpreter command SAVE filename,FAST. The program then can be compiled, prepared, and executed with the BASICGO command. You must specify the FAST option to compile the program.

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To compile, prepare, and execute the BASIC/V program MYPROG, enter:

  BASICGO
  $CONTROL USLINIT
  $COMPILE MYPROG
  $EXIT

The above example begins execution of the BASIC/V compiler, initializes the USL, compiles the program MYPROG, and then exits from the compiler.

The BASICOMP command compiles a program from a "fastsave" file generated by the BASIC/V interpreter. If a USL file is not specified, the BASIC/V compiler stores the object code in the default systemcdefined temporary file $OLDPASS, as shown in the second example, below. You may, however, build a USL file in the permanent file domain, then direct the BASIC/V compiler to store the object code in this file by naming the USL file in the BASICOMP command line. Refer to "Examples."

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To compile the BASIC/V program MYPROG onto the USL named OBJECT, enter:

  BUILD OBJECT;CODE=USL
  BASICOMP, OBJECT
  $CONTROL USLINIT
  $COMPILE MYPROG
  $EXIT

The above example builds the USL file, begins execution of the BASIC/V compiler and specifies the USL named OBJECT, initializes the USL, compiles the fastsave program named MYPROG, and then exits from the compiler.

If you do not choose to build a USL file, the BASICOMP command compiles your program and stores the object code in the default USL file $OLDPASS.

  BASICOMP
  $COMPILE MYRUN
  $EXIT

The above example begins execution of the BASIC/V compiler, accepts commands from $STDINX, and specifies $OLDPASS the USL output and $STDLIST for listing output. It compiles from the fastsave file named MYRUN into a USL named $OLDPASS, and then exits from the BASIC/V compiler.

To run your program, enter:

  PREPRUN $OLDPASS

The BASICPREP command compiles and prepares a program for execution from a " fastsave" file generated by the BASIC/V interpreter. If the progfile parameter is omitted, the prepared program segments are stored in the systemcdefined temporary file $OLDPASS. To save the prepared program in a file other than $OLDPASS, either create a file and specify its file name on the BASICPREP command line, or specify a nonexistent progfile.

A program compiled and prepared with the BASICPREP command may be executed with the MPE/iX RUN command.

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To compile and prepare a program named MYPROG from the BASIC/V fastsave file named MYCOMDS, with the listing directed to the standard list device, enter:

  BASICPREP,MYCOMDS

The file MYPROG is an ASCII file that contains the following BASIC/V compiler commands:

  $CONTROL USLINIT SOURCE
  $COMPILE MYPROG
  $EXIT

The above example initializes the USL and lists the program, compiles the fastsave program MYPROG, and then exits from the compiler.

The BBASIC command is generally used for online programming in HP Business BASIC/V, but it can also be used to interpret HP Business BASIC/V programs submitted in batch mode. In batch mode, the HP Business BASIC/V >EXIT or >:: command is required as the last statement in the command file. HP Business BASIC/V has its own online help facility.

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To enter commands and data from your standard input device, with program listing and output transmitted to the standard output device, use:

  BBASIC

You may also submit commands and data to the HP Business BASIC/V interpreter through input files that you have stored on disk. Files created using the editor must be kept with the UNN (unnumbered) option of the editor's KEEP command. In this example, HP Business BASIC/V interpreter commands and statements are submitted from the command file MYCOMDS. The data that the program uses is stored in the input file MYDATA. The program listing and output are written to the file MYLIST:

  BBASIC MYCOMDS,MYDATA,MYLIST

This command compiles, prepares, and executes a program from a BSAVE file created by the HP Business BASIC/V interpreter. This enables the program to run faster than it would if it were executed by the interpreter.

You may create a BSAVE program file within the HP Business BASIC/V interpreter after it is saved by using the HP Business BASIC/V interpreter >SAVE filename command. The program then can be compiled, prepared, and executed with the BBASICGO command.

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To compile, prepare, and execute the HP Business BASIC/V program MYPROG and send the listing to the disk file LISTFL, enter:

  BBASICGO MYPROG,LISTFL

The BBASICOMP command compiles a source program stored in a BASIC SAVE file generated by the HP Business BASIC/V interpreter. The compiled program executes significantly faster than the corresponding interpreted version.

A BSAVE program file can be created from within the HP Business BASIC/V interpreter after it is written, by using the HP Business BASIC/V interpreter >SAVE filename command. The program may be compiled with the BBASICOMP command, then prepared with the PREP command, and executed with the RUN command .

This command may be issued from a session, job, or program. It may not be used in BREAK. Pressing Break suspends the execution of this command. Entering the RESUME command continues the execution.

To compile the HP Business BASIC/V program MYPROG into the USL named OBJECT, enter:

  BBASICOMP MYPROG,OBJECT

If you do not choose to build a USL file, the BBASICOMP command compiles your program, storing the object code in the default USL file $OLDPASS.

  BBASICOMP MYPROG

If you now want to run your program, use the PREPRUN command:

  PREPRUN $OLDPASS