Commands ABORT to BYE

• ABORT
• ABORTIO/ =ABORTIO
• ABORTJOB/ =ABORTJOB
• ABORTPROC
• ACCEPT
• ALLOCATE
• ALLOW
• ALTACCT
• ALTFILE
• ALTGROUP
• ALTJOB
• ALTLOG
• ALTPROC
• ALTSEC
• ALTSPOOLFILE
• ALTUSER
• ASSOCIATE
• BASIC
• BASICGO
• BASICOMP
• BASICPREP
• BBASIC
• BBASICGO
• BBASICOMP
• BBASICPREP
• BBXL
• BBXLCOMP
• BBXLGO
• BBXLLK
• BREAKJOB
• BUILD
• BYE

ABORT

Syntax

  ABORT

Parameters

Operation Notes

Use

Example

  ABORT

Related Information

Commands

RESUME, SETJCW

Manuals

None

ABORTIO/ =ABORTIO

Syntax

  ABORTIO ldev

  =ABORTIO ldev

Parameters

ldev

The logical device number of the device for which you intend to abort one pending I/O request.

Operation Notes

  NO I/O TO ABORT FOR DEVICE #ldev

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.

Use

Examples

  ABORTIO 53

  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

Related Information

Commands

SHOWDEV

Manuals

Performing System Operation Tasks

ABORTJOB/ =ABORTJOB

Syntax

  ABORTJOB { #Jnnn | #Snnn | [jobname>,]user.acct }

  =ABORTJOB { #Jnnn | #Snnn | [jobname,]user.acct }

Parameters

#Jnnn

A job number.

#Snnn

A session number.

jobname

The name of the job, as identified by the SHOWJOB command.

user

A user name.

acct

An account name.

Operation Notes

  SESSION ABORTED BY SYSTEM MANAGEMENT

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

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

  SESSION ABORTED BY SYSTEM MANAGEMENT

Use

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.

Examples

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

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

  ?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

Related Information

Commands

ALTJOB, BREAKJOB, JOBFENCE, JOBSECURITY, RESUMEJOB, SHOWJOB, STREAM

Manuals

Performing System Operation Tasks

ABORTPROC

Syntax

  ABORTPROC [ [PIN=]{ pinspec }]
            {(pinspec [,pinspec ]...)}
    [;SYSTEM]

Parameters

pinspec

The process(es) to abort. This is a required parameter. The syntax for pinspec is:

[#P]pin[.tid]

where PIN is the Process ID number and TID is an optional thread ID number. A leading "#P" is optional.

To abort more than one process, a list of PINSPECs can be specified. The list is enclosed in parenthesis and individual PINSPECs are separated by commas. If a list is specified it is processed in order, from left to right. ABORTPROC stops processing the list if an error is detected. Duplicate PINs are not detected.

Although a PIN value of zero has meaning in the SHOWPROC and ALTPROC commands, it is invalid in ABORTPROC. To kill yourself use the HPPIN variable, e.g., ABORTPROC !hppin.

Aborting detached system processes requires SM capability as well as specifying the SYSTEM option.

SYSTEM

The SYSTEM option is necessary if the target process is a detached system process. SM capability is required to use the SYSTEM option.

MPE/iX supports 8 process types (shown below). Every process has a process type. Processes with a process type greater than or equal to four (4) are considered system processes. System processes are not abortable unless they have a process type of six (6), indicating they are "detached".

      Process
       Type       Abortable     Restrictions
      ----------------------------------------------- 
      0 User          Y         SM or OP capability.
      1 Son           Y         SM or OP capability.
      2 Usermain      Y         SM or OP capability.
      3 reserved     n/a        n/a
      4 System        N         Not Abortable!
      5 Detached      Y         Must specify ;SYSTEM.
                                SM capability is required.
      6 JSMAIN        N         Not Abortable!
      7 reserved     n/a        n/a

Processes with a process type of 0, 1 or 2 are considered user processes, and are abortable by any user with SM or OP capabilities.

The Command Interpreter (CI) process for all jobs and sessions has a process type of two. Any process that is an immediate child of a CI process has a process type of one. Processes which are descendants of processes with process type 1 or 0, have a process type of 0.

If a user specifies the SYSTEM option, and the process is not a system process (process type < 4), the SYSTEM option is silently ignored.

Operation Notes

Use

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.

Examples

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

NOTE: SM capability is required to abort system processes.

Related Information

Commands

ABORTJOB, ALTPROC, BREAKJOB, RESUME, SHOWPROC

Manuals

MPE/iX Intrinsics Reference Manual

ACCEPT

Syntax

  ACCEPT [ JOBS | DATA ] ,ldev

Parameters

JOBS

The designated device recognizes the JOB and HELLO commands. The device must be interactive to support sessions.

DATA

The designated device recognizes the DATA command. Data-accepting devices are not supported.

NOTE: If you omit both the JOBS and the DATA parameters, then both the JOB and HELLO commands, and the DATA command are allowed.

ldev

The logical device number of the device for which the JOB, HELLO, and/or DATA commands are being enabled.

Operation Notes

Use

Examples

  ACCEPT 19
  SHOWDEV 19
  
  LDEV AVAIL  OWNERSHIP  VOLID ASSOCIATION
   19 AVAIL

  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

Related Information

Commands

REFUSE

Manuals

Introduction to MPE XL for MPE V System Administrators
System Startup, Configuration, and Shutdown Reference Manual

ALLOCATE

Syntax

  ALLOCATE [ PROCEDURE, | PROGRAM, ] name

Parameters

PROCEDURE

The procedure in SL.PUB.SYS to be allocated. The default is PROGRAM.

PROGRAM

The program file to be allocated. Default.

name

The name of the program file or procedure to be allocated.

Operation Notes

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.

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)

Use

Example

  ALLOCATE PROCEDURE,PROC1

Related Information

Commands

DEALLOCATE

Manuals

Introduction to MPE XL for MPE V Programmers

ALLOW

Syntax

  ALLOW FILE=formaldesignator[ ;SHOW]

  ALLOW[ @.@ | user.@ | @.acct | user.acct

    ;COMMANDS=command [ ,command,...]

Parameters

formal- designator

An ASCII file name, which may consist of one to eight alphanumeric characters, beginning with an alphabetic character. It may be fully or partially qualified and may be back-referenced in a file equation.

SHOW

Lists input lines on $STDLIST.

@.@

Grants access to all users whether logged on or not.

user.@

Grants access to a specific user in all accounts.

@.acct

Grants access to all users in a specific account.

user.acct

Grants access to a specific user in a specific account.

command

The names of those commands to which the user is granted access.

Operation Notes

  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

  ALLOW FILE=ALLOWTMP;SHOW

  FILE BACKF=ALLOWTMP
  ALLOW FILE=*BACKF;SHOW

1. Enter ALLOW, followed by Return.

2. At the prompt (>), enter all of the commands you want to allow.

3. When you finish, press Return and enter a colon : as the first character of the new line. (You may also type EXIT.)

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.

  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

Use

Examples

  ALLOW USER.TECH;COMMANDS=REPLY,ABORTIO

  ALLOW
  >MGR.MANUALS;COMMANDS=BREAKJOB
  >EXIT

Related Information

Commands

DISALLOW, SHOWALLOW

Manuals

Performing System Operation Tasks

ALTACCT

Syntax

  ALTACCT acctname [ ;PASS=[ password] ] [ ;FILES=[ filespace]]
    [ ;CPU=[ cpu]]
    [ ;CONNECT=[ connect]] [ ;CAP=[ capabilitylist]]
    [ ;ACCESS=[ (fileaccess)]]
    [ ;MAXPRI=[ subqueuename] ] [ ;LOCATTR=[ localattribute] ]
    [ ;ONVS=volumesetname] [ ;USERPASS=[ {REQ | OPT } ] ] (1)

Parameters

acctname

The name of the account to be altered.

password

The password to be assigned to the account. If you omit password, any existing password is removed. If you omit PASS=, any existing password is unchanged.

filespace

Disk storage limit, in sectors, for the permanent files in the account. The filespace limit cannot be less than the number of sectors currently in use for the account.

cpu

The limit on cumulative CPU-time, in seconds, for the account. This limit is checked only when a job or session is initiated, and, therefore, never causes the job or session to abort. The maximum value allowed is 2,147,483,647 seconds. You may set the counter to zero with the RESETACCT command.

connect

The limit on total cumulative session connect-time, in minutes, allowed the account. This limit is checked at logon. Every time the process terminates the counter is updated. The maximum value allowed is 2,147,483,647 minutes. You may reset the counter to zero with the RESETACCT command.

capabilitylist

Either 1) a list of capabilities, separated by commas, permitted the account, or 2) a list of additions and/or deletions to be applied to the account's existing set of capabilities. Additions and deletions are specified by a "+" or "-" immediately followed by the capability to add or delete, separated by commas.

If "+"/"-" is to be specified in the list, then the list must begin with "+" or "-". For example, CAP=+MR,-PH is legal, but CAP=MR,-PH is not. It is not necessary to prefix each capability to be added or deleted with "+" / "-", as the occurrence of "+" / "-" indicates an action that remains in effect until the indicator changes. For example, CAP=+MR,PH,-PM,DS is equivalent to CAP=+MR,+PH,-PM,-DS

If a capability is removed at the account level, users within the account are also denied that capability. No explicit change to the user's capabilities is necessary. Similarly, if a capability is returned to the account, any users with that capability regain it automatically.

Each capability is denoted by a two letter mnemonic, as follows:

  System Manager     =  SM
  Account Manager     =  AM
  Account Librarian    =  AL
  Group Librarian     =  GL
  Diagnostician      =  DI
  System Supervisor    =  OP
  Network Administrator  =  NA
  Node Manager      =  NM
  Save Files       =  SF
  Access to Nonshareable
  I/O Devices      =  ND
  
  Use Volumes       =  UV
  
  Use Communication
  Subsystem       =  CS
  Programmatic Sessions  =  PS
  User Logging      =  LG
  Process Handling    =  PH
  Extra Data Segments   =  DS
  Multiple RINs      =  MR
  Privileged Mode     =  PM
  Interactive Access   =  IA
  Batch Access      =  BA

Default is AM, AL, GL, SF, ND, IA, BA, except for the SYS account. The SYS account has no true default. It is assigned the maximum account capabilities when the system is delivered and, under normal circumstances, should not be altered.

If a capability is taken away from an account, it is unavailable to users in that account. However, users are not affected by this change until they log off and then log back on.

fileaccess

The restrictions on file access pertinent to this account. Default is R,L,A,W,X:AC, entered as follows:

  ([{ R | L | A | W | X } [ ,...] : { ANY | AC } ] [ ;...] )

The R, L, A, W, and/or X specify modes of access by types of users (ANY and/or AC ) as follows:

  R = READ
  L = LOCK
  A = APPEND
  W = WRITE
  X = EXECUTE

LOCK allows exclusive access to the file. APPEND implicitly specifies LOCK. WRITE implicitly specifies APPEND and LOCK.

The user types are specified as follows.

  ANY = Any user
  AC = Member of this account only

subqueuename

Name of the highest priority subqueue that can be requested by any process of any job/session in the account, specified as AS, BS, CS, DS, or ES. When you specify ;MAXPRI= without a value, subqueuename defaults to CS.

CAUTION: User processes executing in the AS or BS subqueues can deadlock the system. If you assign these subqueues to nonpriority processes, other critical system processes may be prevented from executing. Exercise extreme caution when choosing subqueues.

localattribute

Local attribute of the account, as defined at the installation site. This is a double-word bit map, of arbitrary meaning, that might be used to further classify accounts. While it is not involved in standard MPE/iX security provisions, it is available to processes through the WHO intrinsic. Programmers may use localattribute in their own programs to provide security. Default is double word 0 (null).

volume-setname

The MPE/iX volume set in which the account is to be altered. This volume set must be already defined and recognized by the system. When ONVS=volumesetname is specified, the volume set directory is assumed. When ONVS= is specified without volumesetname, the system directory is assumed.

MPE/iX volume set names consist of from 1 to 32 characters, beginning with an alphabetic character. The remaining characters may be alphabetic, numeric, the underscore, or periods.

This parameter only works with the FILES parameter (all other parameters are ignored).

REQ

USERPASS=REQ specifies that all users in the account must have a non-blank password. It is available only if the HP Security Monitor has been installed.

OPT

USERPASS=OPT specifies that users in this account may or may not have passwords. If you do not use the USERPASS parameter, the old value remains. It is available only if the HP Security Monitor has been installed.

Operation Notes

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.

Use

Examples

  ALTACCT AC2;PASS=GLOBALX;FILES=50000

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

Related Information

Commands

ALTGROUP, ALTUSER, LISTACCT, LISTGROUP, LISTUSER, NEWACCT, NEWGROUP, NEWUSER, RESETACCT

Manuals

Performing System Management Tasks

ALTFILE

Syntax

  ALTFILE[ FILE=] filename [ ] ;OWNER=ownername] ]
    [ [ ;GROUPID=] POSIXgroupname]

Parameters

filename

The filename of the object to be altered, specified in either MPE or HFS syntax. The filename may name a file, hierarchical directory, root, MPE group or account. Note that MPE groups or accounts can ONLY be named via HFS (Hierarchical File System) syntax. Temporary files are not recognized.

This is a required parameter. You may not use wildcards, back-reference a file equation, or name a system-defined file such as $NULL.

If the filename is in MPE syntax and it has a lockword, do NOT include the lockword on the command line, or you will get an error.

ownername

The name of the user who will become the owner (UID) of filename. This ownername must already exist on the system. Default is for the UID of the file to remain unchanged. Note that no qualification is done on this name; it must be fully specified. To have the ownername upshifted, enclose it in quotes.

POSIXgroupname

The name of the POSIX group (GID) that this file will belong to. This POSIXgroupname must already exist on the system. You cannot use this parameter to change the GID of an MPE group or account. Default is for the file to retain its previous GID. To have POSIXgroupname upshifted, enclose it in quotes.

Operation Notes

• The file's account manager (your logon account matches the GID of the file and you have MPE/iX account manager (AM) capability). In this case, ownername must specify a user belonging to the account manager's logon account.

• A system manager (a user who has the MPE/iX system manager (SM) user capability). In this case, ownername may specify any user existing in the user database.

• The file owner (your logon name matches the UID of the file). In this case, POSIXgroupname must specify your logon account.

• The file's account manager (your logon account matches the GID of the file and you have the MPE/iX account manager (AM) capability). In this case, POSIXgroupname must specify the account manager's logon account.

• A system manager (you have MPE/iX system manager (SM) capability). In this case, POSIXgroupname may specify any GID existing in the group database.

Related Information

Commands

ALTSEC, LISTFILE, RELEASE, SECURE

Manuals

Performing System Management Tasks

ALTGROUP

Syntax

  ALTGROUP groupname [ .acctname]
    [ ;PASS=[ password]] [ ;CAP=[ capabilitylist] ]
    [ ;FILES=[ filespace] ] [ ;CPU=[ cpu] ]
    [ ;CONNECT=[ connect] ] [ ;ACCESS=[ (fileaccess)] ]
    [ ;ONVS=volumesetname] [ ;HOMEVS=volumesetname]

Parameters

groupname

The name of the group whose attributes are to be changed.

acctname

The name of the account in which the group is to reside. System manager (SM) capability is required to use this parameter.

password

The password to be assigned to the group, which is used to verify logon and access only. If the PASS parameter is omitted, no change is made. If PASS is used and password is omitted, the existing password is removed. If PASS is used and password is specified the existing password is changed; if there is no existing password for the group a password is created.

capabilitylist

Either 1) a list of capabilities, separated by commas, permitted this group, or 2) a list of additions and/or deletions to be applied to the group's existing set of capabilities. Additions and deletions are specified by a "+" or "-" immediately followed by the capability to add or delete, separated by commas.

If "+"/"-" is to be specified in the list, then the list must begin with "+" or "-". For example, CAP=+MR,-PH is legal, but CAP=MR,-PH is not.

It is not necessary to prefix each capability to be added / deleted with "+" / "-", as the occurrence of "+" / "-" indicates an action that remains in effect until the indicator changes. For example, CAP=+MR,PH,-PM,DS is equivalent to CAP=+MR,+PH,-PM,-DS.

Each capability is denoted by a two letter mnemonic, as follows:

  Process Handling   =    PH
  Extra Data Segments =    DS
  Multiple RINs    =    MR
  Privileged Mode   =    PM
  Interactive Access  =    IA
  Batch Access     =    BA

Default is IA, BA except for the PUB group of the SYS account which has no true default. It is assigned the maximum group capabilities when the system is delivered and should not normally be changed.

filespace

Disk storage limit, in sectors, for the permanent files of the group. A group's filespace cannot be set to a value greater than the corresponding limits currently defined for the group's account. Nor can a group's filespace be set to a value less than the actual number of sectors in use in that group. Default is unlimited file space.

cpu

The limit on the total cumulative CPU-time, in seconds, for the group. This limit is checked only when a job or session is initiated; the limit never causes a job/session to abort. The maximum value allowed is 2,147,483,647 seconds. If the limit is exceeded, users with account manager capability are warned when logging on; other users are denied access.

The CPU limit for a group cannot be set to a value greater than the corresponding limit currently defined for the group's account. Default is unlimited CPU-time. The counter may be set to zero with the RESETACCT command.

connect

The limit on the total cumulative session connect-time, in minutes, that the group is allowed. This limit is checked at logon, and whenever the session initiates a new process. The maximum value allowed is 2,147,483,647 minutes. If the limit is exceeded, users with account manager capability are warned when logging on; other users are denied access.

A group's connect limit cannot be set to a value greater than the corresponding limit currently defined for the group's account. Default is unlimited connect-time. The counter may be set to zero with the RESETACCT command.

fileaccess

The restriction on file access pertinent to this group. Default is R,X:ANY;A,W,L,S:AL,GU for the public group (PUB); and R,A,W,L,X,S:GU for all other groups, where R, L, A, W, and X specify modes of access by types of users (ANY, AC, GU, AL, GL) as follows:

  R =  READ
  L =  LOCK
  A =  APPEND
  W =  WRITE
  X =  EXECUTE
  S =  SAVE

LOCK allows exclusive access. APPEND implicitly specifies LOCK. WRITE implicitly specifies APPEND and LOCK.

The user types are specified as follows:

  ANY =  Any user
  AC =  Member of this account only
  GU =  Member of this group only
  AL =  Account librarian user only
  GL =  Group librarian user only

To specify two or more user or access types, separate them by commas.

ONVS

A particular volume set for which the group attributes are to be changed. The volume set must be already defined and recognized by the system. If you specify ONVS, the only other parameter that works with it is the FILES parameter. If volumesetname is omitted from the ONVS= parameter, or you omit ONVS, the operation is performed on the system volume set.

HOMEVS

Changes the home volume set from the current set to the set specified by volumesetname. You may do this only if the group on the current home system volume set is empty and not in use; no one is logged onto that group.

volume setname

The full name of the MPE/iX volume set, consisting of from 1 to 32 characters, beginning with an alphabetic character. The remaining characters may be alphabetic, numeric, the underscore, or periods.

You cannot change the home volume set if the home volume set is the system volume set, and it contains files. If it contains no file, you can change the home volume set.

Consider the following when changing the home volume set:

• If the home volume set is the system volume set, no files may exist in the group and the group may not be in use (no users may be logged onto the group). Otherwise, the command fails.

• If the current home volume set is not the system volume set but the volume set is mounted, no files may exist in the group on that volume set, and the group may not be in use. Otherwise, the command fails.

• If the current home volume set is not the system volume set and it is not mounted, it may be changed.

It is permissible to reassign a group to a different volume set despite the presence of files belonging to groupname. This is possible provided that the old volume set is not the system volume set and the groupname is not currently bound to its home volume set. This binding occurs automatically when the volume set is mounted; it occurs explicitly when the MOUNT or VSOPEN commands are invoked; it occurs implicitly when the FOPEN intrinsic is invoked.

Operation Notes

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.

Use

Examples

  ALTGROUP GROUPX;PASS=PASS2

  ALTGROUP LEILA;ONVS=TIME_LORD;FILES=10000

  ALTGROUP LEILA;HOMEVS=DICHONDRITE

Related Information

Commands

ALTACCT, ALTUSER

Manuals

Volume Management Reference Manual

ALTJOB

Syntax

  ALTJOB[ JOB=] { #Jnnn  #Snnn }
    [ ;INPRI=inputpriority] [ ;OUTDEV={ ldev devclass } ]
    [.HIPRI][;JOBQ=queuename]

Parameters

#Jnnn

A job number.

#Snnn

A session number. (Although syntactically correct, this parameter is rarely used: sessions do not wait.)

inputpriority

The new input priority (0 = lowest; 14 = highest).

ldev or devclass

The logical device number or device class name of the destination device job's $STDLIST.

HIPRI

Allows the OP or SM to bypass the joblimit, see the JOB command for more detail.

queuename

The name of the job queue whose limit is being changed.

Operation Notes

Use

Example

  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

Related Information

Commands

JOBFENCE, JOBSECURITY, LISTJOBQ

Manuals

Performing System Operation Tasks

ALTLOG

Syntax

  ALTLOG logid [ ;LOG=logfile { ,DISC ,TAPE } ]
    [ ;PASS=password[ { ;AUTO ;NOAUTO } ]

Parameters

logid

The logging identifier whose attributes are to be changed. This identifier must contain from one to eight alphanumeric characters, beginning with an alphabetic character.

logfile

The name of the file to receive data from the logging procedure. This name must contain from one to eight alphanumeric characters, beginning with an alphabetic character. You must specify the device class on which log file resides, either DISC or TAPE.

password

The new password for the logging identifier. This password must contain from one to eight alphanumeric characters, beginning with an alphabetic character.

AUTO

Initiates an automatic CHANGELOG if the current log file becomes full. This option is ignored is TAPE is specified. Refer to the CHANGELOG command.

NOAUTO

Prevents the initiation of an automatic CHANGELOG. A CHANGELOG is not performed if the current log file becomes full. Default.

Operation Notes

Use

Example

  ALTLOG KIM;LOG=C,DISC

Related Information

Commands

CHANGELOG, GETLOG, LISTLOG, SHOWLOGSTATUS

Manuals

User Logging Programmer's Guide
System Startup, Configuration, and Shutdown Reference Manual

ALTPROC

Syntax

  ALTPROC[ [ PIN=] { pinspec (pinspec [ ,pinspec ] ...) }
    [ ;JOB=] { jobspec (jobspec [ ,jobspec ] ...) } ]
    [ [ ;PRI=] pri [ ;WG= ] { workgrp NATURAL_WG } ]
    [ { ;TREE ;NOTREE }]
    [{ ;USER ;ANYUSER } ]
    [ ;SYSTEM]

Parameters

pinspec

The process(es) you want to alter. This is a required parameter, unless you specify jobspec. If you omit both, you will get an error.

The pinspec, expressed [#p ]pin, is a Process Identification Number (PIN). If pinspec is 0, then the caller's pin is used. To alter system processes, you must have SM capability and specify the SYSTEM option.

NOTREE is the default for all pinspec target processes, and can be overridden with the TREE option.

The USER and ANYUSER options do not apply to pinspec.

jobspec

The name of the job or session whose processes are to be altered. A jobspec can be any of the following, jobnumber, username, @S, @J, or @.

• The jobnumber must be in the form of either #Jnnn or #Snnn.

• The username must be in the form user[.account]. If there is more than one job/session matching the same username, they will all be altered.

• Wildcards have the following meanings:

  • @S - all sessions,

  • @J - all jobs,

  • @ - all sessions and jobs

The USER and ANYUSER options apply only to jobspec and only if jobspec is wildcarded. The USER option, which is the default, alters only processes matching the user's name, while the ANYUSER option alters all processes matching the wildcarded jobspec. For example, if the user's name is STEVE.UI and you enter the command shown below, then only job processes logged on as STEVE.UI are altered.

  :ALTPROC job=@j;pri=cs

However, if you add anyuser to the same command as shown below, then all job processes are altered.

  :ALTPROC job=@j;pri=cs;anyuser

TREE is the default for all jobspec target processes, and can be overridden with the NOTREE option.

The SYSTEM option is ignored for all jobspec target processes.

The jobspec is optional as long as a pinspec is supplied. If both are omitted, an error is reported.

pri

The queue or absolute priority for the process. If omitted, the priority is unchanged.

CAUTION: Exercise extreme caution when altering a process's priority, scheduling queue attribute, or workgroup membership. Such a change can significantly impact system performance.

NOTE: For Workload Manager Users Avoid using the ;PRI= option to explicitly change a process. If you have created user-defined workgroups that have ;MEMB_QUEUE as membership criteria, use of the ;PRI= option may change the workgroup. Instead, use either the ;WG=workgrp or ;WG=NATURAL_WG option, explained below, to move target processes into existing workgroups. Using ;WG= to explicitly change a workgroup should be a temporary measure, and used rarely. Instead, adjust workgroup membership criteria to ensure that desired processes become natural members of the workgroup. If you specify both the ;WG= and ;PRI= in the ALTPROC command line, you will get an error.

The pri value may be one of the following:

• A scheduling queue value {BS,CS,DS,ES} sets the queue attribute of the target process(es). If a user-defined workgroup does not capture the process, then the process will fall into to the corresponding system-defined default workgroup at the base priority (subject to decay as it consumes CPU). To assign a scheduling queue value, you must have OP capability.

• A queue manager value {BM,CM,DM,EM} sets the queue attribute of the target process(es). If a user-defined workgroup does not capture the process, then the process will fall into the corresponding system-defined default workgroup at the base priority (non-decayable). To assign a queue manager value, you must have SM capability.

• An absolute priority {nnn} sets the priority of the process to the specified value that will not decay. The workgroup of the process will not be changed (the process will have the same timeslice value). Note that the priority specified need not fall between the base and limit priorities of the workgroup. To assign an absolute priority value, you must have SM capability.

If you do not have SM capability, then your MAXPRI value represents the highest priority that you can assign a process. A warning appears when the specified priority exceeds MAXPRI. MAXPRI is ignored for System Manager (SM) capability.

workgrp

A workgroup value {workgrp} moves the target process(es) to the specified workgroup. A process moved in this manner is considered an artificial member of the workgroup (the process was placed in workgroup explicitly, rather than naturally by meeting the membership criteria specified for the workgroup).

A process remains an artificial member of its assigned workgroup until either the workgroup is purged or the process' explicit assignment is changed (via ALTPROC or an AIF call). An artificial member is not affected by a system-wide scan or by the changing of its process attributes used to determine workgroup membership. A workgroup specification requires SM capability and can only be used to modify the workgroup assignment of user processes.

You cannot specify both the ;WG= and ;PRI= in the ALTPROC command line. Workload Manager users should use ;WG= instead of ;PRI=.

NATURAL_WG

The natural workgroup specification {NATURAL_WG} releases one or more process(es) from their explicit workgroup assignment, allowing them to migrate to their natural workgroup. A natural workgroup specification requires SM capability.

TREE

This option alters each process specified as well as all of its descendants. TREE is the default for all jobspec target processes. If you specify both TREE and SYSTEM, you will see a warning that TREE will be ignored.

NOTREE

This option alters only the processes specified. Descendant processes will not be altered. NOTREE is the default for all pinspec target processes.

USER

The USER option applies only when jobspec is wildcarded. It alters only processes matching the user's name. USER is the default.

ANYUSER

The ANYUSER option applies only when jobspec is wildcarded. It alters all jobspec target processes, regardless of their owners.

SYSTEM

Use the SYSTEM option if the target process specified in pinspec is a system process. SM capability is required for the SYSTEM option. SYSTEM is ignored for all jobspec processes and when you specify a workgroup or natural workgroup. If you specify both SYSTEM and TREE, you see a warning that TREE will be ignored.

CAUTION: Exercise extreme care when altering system processes since doing so can significantly degrade system efficiency.

Operation Notes

Example

  :ALTPROC #p605; tree; wg=DS_Default

  :ALTPROC #p605; tree; pri=DS

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

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

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

  :ALTPROC 0;pri=CM

  :ALTPROC job=mgr.payroll; pri=155

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

Related Information

Commands

SHOWPROC, TUNE, SHOWQ, NEWWG, ALTWG, PURGEWG, SHOWWG

Manuals

MPE/iX Intrinsics Reference Manual
Using the HP 3000 Workload Manager

ALTSEC

• files

• hierarchical directories

• devices

• device classes

Syntax

  ALTSEC objectname [ ,{FILENAME LDEV DEVCLASS } ]
    [ ;[ ACCESS=] (fileaccess[ ;[ fileaccess] [ ;...] ] )]
    [{;NEWACD=|;ADDPAIR=|;REPPAIR=}{(acdpair [;...])^filereference }]
    [ ;DELPAIR= { (userspec [ ;userspec] [ ;...] ) ^filereference }]
    [{;REPACD=} {(acdpair [ ;...] ) ^filereference objectname }]
    [ ;COPYACD= objectname { ,FILENAME ,LDEV } ] [ ;DELACD] [ ;MASK]

Parameters

objectname

Specifies the actual file designator, directory name, logical device number, or device class whose security provisions you want to alter.

Either MPE or hierarchical file system (HFS) file name Syntax may be used for the actual file designator of the file or directory whose access permissions are to be altered.

You can only use wildcard characters with MPE Syntax files that reside in a group.

A logical device number must be a numeric value configured on the system, or an @ sign, that indicates all devices on the system. A device class name must be configured on the system.

File equations are ignored during resolution of the object name to avoid having accidental file equation references cause unintentional changes to an object's access permissions.

MPE Syntax

You can include MPE file name Syntax but not RFA information. If the object is an MPE Syntax file, its format is:

  filename[/lockword][.groupname[.acctname]]

You may specify file lockwords for files protected by active lockwords unless the objects are also protected by a current ACD. In a batch job, if a lockword exists on a file, you must specify it. In a session, if a lockword exists and is omitted, MPE/iX will prompt you for it.

HFS Syntax

You must begin file designators using HFS file name Syntax with either a dot (.) or a slash (/). The maximum length is 255 characters (including the "./" or "/").

The objectname parameter is followed by one of the three type
identifiers listed below.

FILENAME

Indicates that objectname refers to either a file or directory. This is the default if a type identifier is not specified.

LDEV

Indicates that objectname refers to a logical device number.

DEVCLASS

Indicates that objectname refers to a device class.

ACCESS

Optional keyword that indicates a fileaccess specification follows. This option affects security at the file level only. If the file is protected by an ACD, the ACD overrides the file access mask.

fileaccess

File access mask specifications, entered as follows:

  { R L A W X } [,...] : { ANY AC GU AL GL CR } [,...]

The R, L, A, W, and X specify modes of access by types of users (ANY, AC, GU, AL, GL, CR) as follows:

  R  =  READ
  L  =  LOCK
  A  =  APPEND
  W  =  WRITE
  X  =  EXECUTE

LOCK allows opening the file with dynamic locking option. APPEND implicitly specifies LOCK. WRITE implicitly specifies APPEND and LOCK. You may specify two or more modes if you separate them by commas.

The user types are specified as follows:

  ANY = Any user
  AC = Member of this account only
  GU = Member of this group only
  AL = Account librarian user only
  GL = Group librarian user only
  CR = Creator

You may specify two or more user types if you separate them by commas. The default is R,L,W,A,X:ANY. The colon (:) separating one or more modes from one or more user types is required punctuation in the specification of fileaccess.

NEWACD

Creates a new ACD for the specified object. NEWACD is used when an ACD does not currently exist. It must be followed by valid ACD pair(s) as described below.

REPACD

Indicates "replace ACD". Use REPACD to replace an entire existing ACD for the specified object, or to copy an ACD from an existing objectname to the specified objectname where objectname refers to a file. (You cannot use REPACD to copy ACDs between devices.) The REPACD parameter must be followed by valid ACD pair(s) as described below.

ADDPAIR

Adds a new ACD pair to an existing ACD. It must be followed by valid ACD pair(s) as described below.

REPPAIR

Replaces an existing ACD pair in an existing ACD. You must follow this with a valid ACD pair(s) as described below. A new ACD pair will replace an existing ACD pair if it has the same user and account name.

acdpair

An access control definition pair. Like the fileaccess parameter this consists of a modes part and a userspec part. The modes part is separated from the userspec part by a colon (:). Acceptable modes for files are:

  R : read file access
  W : write file access
  L : lock file access
  A : append file access
  X : execute file access
  NONE : no access
  RACD : copy or read the ACD permission

Acceptable modes for directories are:

  CD : create directory entries access
  DD : delete directory entries access
  RD : read directory entries access
  TD : traverse directory entries access
  NONE : no access
  RACD : copy or read the ACD permission

File ACD pairs may contain R, W, L, A, X, NONE, and RACD. Directory ACD pairs may contain CD, DD, RD, TD, NONE, and RACD.

The userspec part consists of

• a fully qualified user name (username.accountname)

• the file owner represented as $OWNER

• the file group represented as $GROUP

• the file group mask represented as $GROUP_MASK

• @.accountname, which represents all users in the account accountname

• @.@, which represents all users in the system

  You cannot use wildcards in any other manner within a user specification.

A typical ACD consisting of three ACD pairs might look like this:

  (R,W:ENGR.MFG;R,W,RACD:@.MRKT;R:@.@)

This ACD would allow Read and Write access to the ENGR user of the MFG account; Read and Write access to any user of the MRKT account along with the ability to read or copy the ACD; and Read access to any user in any account.

^filereference

A file containing one or more ACD pairs. ACD pairs must be separated by semi-colons and may be placed on separate lines. A single ACD pair may not span more than one line. The file name must be preceded by the ^ sign (caret symbol) to indicate that the designated file contains the ACD definition. This is known as an indirect file.

The ALTSEC command fails if the indirect file does not contain a syntactically correct ACD. ACD pairs may be on separate lines, but a pair may not span lines. Parentheses are optional when defining an acdpair within an indirect file.

The file reference may be specified using MPE or HFS file name Syntax. For example:

filename [/lockword] [.group [.account]]

If the file has an active lockword, you must be specify it. ACDs override lockwords. Lockwords can only be specified in file references using MPE name Syntax. Unqualified file names are relative to the current working directory.

DELPAIR

(Indicates "delete pair"). Use to delete one or more ACD pairs in an existing ACD). DELPAIR must be followed by a valid userspec.

userspec

Username and accountname, the same as the userspec described above in acdpair. A wildcard (@) may be used for the username or both the username and accountname together. A wildcard may not be specified for the accountname unless it is also specified for the username.

COPYACD

(Indicates "copy ACD"). Use COPYACD to copy an ACD from an existing objectname to the specified objectname. ACDs can be copied only between like objects. You must specify FILENAME or LDEV. FILENAME is the default. You cannot copy an ACD from a device class (DEVCLASS), although you may copy to all devices on the system by specifying the @ sign as the target device.

DELACD

(Indicates "delete ACD"). Use DELACD to delete all ACD pairs from the specified objectname. ACDs may be removed only from devices and files in MPE groups. The file access matrix controls access to a file when an ACD is deleted.

MASK

(Indicates "recalculate MASK"). Use MASK to recalculate the ACD file group class mask ($GROUP_MASK) access permissions.

Operation Notes

• All hierarchical directories

• All files under hierarchical directories

• All files directly under MPE/iX groups where the file GID does not match the GID of the accound and group in which the file is located. One way this occurs would be if you rename a file from an MPE group outside the account to another MPE group.

File Access Matrix Examples

  ALTSEC FDATA;ACCESS=(W:CR)

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

ACD Examples

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

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

  ALTSEC FDATA;DELPAIR=(@.@)

  ALTSEC FDATA;DELACD

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

  ALTSEC TERM,DEVCLASS;COPYACD=5,LDEV

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

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

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

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

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

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

Related Information

Commands

LISTF, LISTFILE, RELEASE, SECURE, SHOWDEV, and the fileaccess parameter for the ALTACCT, ALTGROUP, NEWACCT and NEWGROUP commands.

Manuals

None

ALTSPOOLFILE

Syntax

  ALTSPOOLFILE { #Onnn | ldev1 }
    { ;PRI=outputpriority |
      ;COPIES=numcopies   |
      ;DEV={ ldev2  devclass }
    [ ;DEFER ] [ ;...]

Parameters

#Onnn

The output device file identification of a spoolfile.

ldev1

The logical device number of the device where an ACTIVE spoolfile currently resides.

outputpriority

The output priority of the designated device file (0 = lowest; 14 = highest).

numcopies

The number of copies to be produced from the designated device file. Range is 1 through 127; default is 1.

ldev2 or devclass

The logical device number or device class name of the spoolfile's destination device. If ACTIVE, the file is returned to the READY state. It may immediately become ACTIVE on ldev2 if all requirements are met.

DEFER

Immediately changes the output priority of an ACTIVE or READY spoolfile to 0. If ACTIVE, the file is returned to the READY state.

Operation Notes

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.

Use

Examples

  ALTSPOOLFILE #O86;DEFER

  ALTSPOOLFILE 6;DEFER

  ALTSPOOLFILE #O123;PRI=3

Related Information

Commands

OUTFENCE

Manuals

Native Mode Spooler Reference Manual

ALTUSER

Syntax

  ALTUSER username[ .acctname]
    [ ;PASS=[ password] ] [ ;CAP=[ capabilitylist] ]
    [ ; MAXPRI=[ subsueuename] ] [ ;LOCATTR=[ localattribut] ]
    [ ;HOME=[ homegroupname] ] [ ;UID=[ uid]
    [ ;USERPASS=[ req  opt ] [ Expired] ]

Parameters

username

The name assigned to the user within a logon account.

acctname

The account in which the user is to reside. System manager (SM) capability is required to use this parameter.

password

The password to be assigned to the user. If password is omitted, any existing password is removed. If PASS= is omitted, any existing password is unchanged.

capabilitylist

Either 1) a list of capabilities, separated by commas, permitted to this user, or 2) a list of additions and/or deletions to be applied to the user's existing set of capabilities. Additions and deletions are specified by a "+" or "-" immediately followed by the capability to add or delete, separated by commas.

If "+"/"-" is to be specified in the list, then the list must begin with "+" or "-". For example, CAP=+MR,-PH is legal, but CAP=MR,-PH is not. It is not necessary to prefix each capability to be added or deleted with "+" / "-", as the occurrence of "+" / "-" indicates an action that remains in effect until the indicator changes. For example, CAP=+MR,PH,-PM,DS is equivalent to CAP=+MR,+PH,-PM,-DS.

The capabilities allowed to users are restricted by the capabilities assigned to the user's account. If a capability is absent at the account level, users within the account are also denied that capability, whether or not it is explicitly assigned to them.

Each capability is denoted by a two-letter mnemonic as follows:

  System Manager    =  SM
  Account Manager    =  AM
  Account Librarian   =  AL
  Group Librarian    =  GL
  Diagnostician     =  DI
  System Supervisor   =  OP
  Network Administrator =  NA
  Node Manager     =  NM
  Save Files      =  SF
  Access to Nonshareable
  I/O Devices     =  ND
  Use Volumes      =  UV
  Create Volumes    =  CV
  Use Communication
  Subsystem        CS
  Programmatic Sessions =  PS
  User Logging     =  LG
  Process Handling   =  PH
  Extra Data Segments  =  DS
  Multiple RINs     =  MR
  Privileged Mode    =  PM
  Interactive Access  =  IA
  Batch Access     =  BA
  Programmatic Sessions =  PS

Default is SF, ND, IA, and BA. Note that CV automatically gives the user UV capability, and removal of UV results in automatic removal of CV.

subqueuename

The name of the highest priority subqueue that may be requested by any process of any job/session initiated by the user. This parameter is specified as AS, BS, CS, DS, or ES, but cannot be greater than that specified with the NEWACCT or ALTACCT commands. The subqueuename defined for the user is checked against the subqueuename defined for the account at logon, and the lower priority of the two is used as the maximum priority restricting all processes of the job/session. Also, the priority requested by the user at logon is checked against the subqueuename defined for the user, and the user is granted the lower of these two values. Default is CS.

CAUTION: Processes capable of executing in the AS or BS subqueues can deadlock the system. By assigning nonpriority processes to these subqueues, you may prevent critical system processes from executing. Exercise extreme care when assigning processes to the AS or BS subqueue.

localattribute

Defined at the installation site, this arbitrary double word bit map is used to further classify users. While it is not part of standard MPE/iX security provisions, programmers may define it (through the WHO intrinsic) to enhance the security of their own programs. The bit map for the user local attributes must be a subset of the bit map for the account local attributes. The ALTUSER command checks the local attributes of the user with those of the account. Default is double word 0 (null).

homegroupname

The name of an existing group assigned as the home group for this user. The first user established when an account is created, by default, has PUB assigned as the home group. Subsequent new users, by default, have no home group assigned. If no home group is assigned, the user must always specify an existing group when logging on.

uid

User ID to be altered for the account manager in the user database. The uid parameter must be a unique positive (non-zero) 32-bit integer.

Req

USERPASS=REQ specifies that all users in the account must have a non-blank password. It is available only if the HP Security Monitor has been installed.

Opt

USERPASS=OPT specifies that users in this account may or may not have passwords. If you do not use the USERPASS parameter, the old value remains. It is available only if the HP Security Monitor has been installed.

Expired

The password expires immediately. The user cannot logon without selecting a new password. It is only available if the HP Security Monitor has been installed.

Operation Notes

Use

Examples

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

  ALTUSER JONES;PASS=JJ;MAXPRI=DS

Related Information

Commands

ALTACCT, ALTGROUP, LISTUSER, NEWACCT, NEWUSER

Manuals

Performing System Management Tasks

ASSOCIATE

Syntax

  ASSOCIATE devclass

Parameters

devclass

The name of a logical device class configured with SYSGEN.

Operation Notes

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

Use

Example

  ASSOCIATE TAPE

Related Information

Commands

DISASSOCIATE

Manuals

Performing System Operation Tasks

BASIC

Syntax

  BASIC [commandfile] [,[inputfile] [,listfile] ]

Parameters

commandfile

Actual file designator of the source file or device from which BASIC/V commands and statements are input. This can be any ASCII input file. Formal file designator is BASCOM. Default is $STDINX.

inputfile

Actual file designator of the file containing data input for a BASIC/V program. This can be any ASCII input file. Formal file designator is BASIN. Default is $STDINX.

listfile

Actual file designator of the destination file for the program listing and output. This can be any ASCII output file. Formal file designator is BASLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BASCOM, BASIN, and BASLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Examples

  BASIC

  BASIC MYCOMDS,MYDATA,MYLIST

Related Information

Commands

BASICGO, BASICOMP, BASICPREP

Manuals

BASIC/V Compiler Manual
MPE Segmenter Reference Manual

BASICGO

Syntax

  BASICGO [commandfile] [,listfile]

Parameters

commandfile

Actual file designator of the input file from which the BASIC/V compiler commands are read. This can be any ASCII input file. Formal file designator is BSCTEXT. Default is $STDINX.

listfile

Actual file designator of the file to which the program listing is written. This can be any ASCII output file. Formal file designator is BSCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BSCTEXT and BSCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Example

  BASICGO
  $CONTROL USLINIT
  $COMPILE MYPROG
  $EXIT

Related Information

Commands

BASIC, BASICOMP, BASICPREP

Manuals

BASIC/V Compiler Reference Manual
MPE Segmenter Reference Manual

BASICOMP

Syntax

  BASICOMP [commandfile] [,[uslfile] [,listfile] ]

Parameters

commandfile

Actual file designator of the input file from which the BASIC/V compiler commands are read. This can be any ASCII input file. Formal file designator is BSCTEXT. Default is $STDINX.

uslfile

Actual file designator of the user subprogram library (USL) file to which the object code is written, which can be any binary output file with a file code of USL or 1024. Its formal file designator is BSCUSL. If the uslfile parameter is omitted, the object code is saved to the temporary file $OLDPASS. If entered, this parameter specifies that the file was created in one of four ways:

• By using the SAVE command to save the default USL file $OLDPASS, created by a previous compilation.

• By building the USL with the MPE segmenter command BUILDUSL. Refer to the MPE Segmenter Reference Manual (30000-90011).

• By creating a new USL file with the MPE/iX BUILD command and a file code of USL or 1024.

• By specifying a nonexistent uslfile parameter, thereby creating a permanent file of the correct size and type.

listfile

Actual file designator of the file on which the program listing is written. This can be any ASCII output file. Formal designator is BSCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BSCTEXT, BSCUSL, and BSCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Examples

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

  BASICOMP
  $COMPILE MYRUN
  $EXIT

To run your program, enter:

  PREPRUN $OLDPASS

Related Information

Commands

BASIC, BASICGO, BASICPREP

Manuals

BASIC/V Compiler Reference Manual
MPE Segmenter Reference Manual

BASICPREP

Syntax

  BASICPREP [commandfile] [,[progfile] [,listfile] ]

Parameters

commandfile

Actual file designator of the input file from which the BASIC/V compiler commands are read. This can be any ASCII file. Formal file designator is BSCTEXT. Default is $STDINX.

progfile

Actual file designator of the program file on which the prepared program segments are written. When progfile is omitted, the MPE segmenter creates the program file, which resides in the temporary file domain as $OLDPASS. To create your own program file, do so in one of two ways:

• By using the BUILD command and specifying a file code of 1029 or PROG and a numextents value of 1. This file is then used by the PREP command.

• By specifying a nonexistent file in the progfile parameter, in which case a temporary job file of the correct size and type is created.

listfile

Actual file designator of the file to which the listing is written. This can be any ASCII output file. Formal file designator is BSCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BSCTEXT and BSCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Examples

  BASICPREP,MYCOMDS

  $CONTROL USLINIT SOURCE
  $COMPILE MYPROG
  $EXIT

Related Information

Commands

BASIC, BASICGO, BASICOMP

Manuals

BASIC/V Compiler Reference Manual

BBASIC

Syntax

  BBASIC [commandfile] [,[inputfile] [,listfile] ]

Parameters

commandfile

Actual file designator of the source file or device from which HP Business BASIC/V commands and statements are input. This can be any ASCII input file. Formal file designator is BASCOM. Default is $STDINX.

inputfile

Actual file designator of the file containing data input for a HP Business BASIC/V program. This can be any ASCII input file. Formal file designator is BASIN. Default is $STDINX.

outfile

Actual file designator of the destination file for the program listing and output. This can be any ASCII output file. Formal file designator is BASOUT. Default is $STDLIST.

NOTE: The formal file designators used in this command (BASCOM, BASIN, and BASOUT) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Example

  BBASIC

  BBASIC MYCOMDS,MYDATA,MYLIST

Related Information

Commands

BBASICGO, BBASICOMP, BBASICPREP

Manuals

HP Business BASIC/XL Reference Manual
MPE Segmenter Reference Manual

BBASICGO

Syntax

  BBASICGO infile [,listfile]

Parameters

infile

Actual file designator of the BSAVE file containing the HP Business BASIC/V program to be compiled. Formal file designator is BBCIN.

listfile

Actual file designator of the file to which the program listing is written. This can be any ASCII output file. Formal file designator is BBCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BBCIN and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. Refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Example

  BBASICGO MYPROG,LISTFL

Related Information

Commands

BBASIC, BBASICOMP, BBASICPREP

Manuals

HP Business BASIC/XL Reference Manual
MPE Segmenter Reference Manual

BBASICOMP

Syntax

  BBASICOMP infile [,[uslfile] [,listfile] ]

Parameters

infile

Actual file designator of the BSAVE file containing the HP Business BASIC/V program to be compiled. Formal file designator is BBCIN.

uslfile

Actual file designator of the user subprogram library (USL) file on which the object program is written, which can be any binary output file with file code of USL or 1024. Its formal file designator is BBCUSL. If the uslfile parameter is omitted, the object code is saved to the temporary file $OLDPASS. If entered, this parameter specifies that the file was created in one of four ways:

• By using the SAVE command to save the default USL file $OLDPASS created by a previous compilation.

• By building the USL with the MPE segmenter command BUILDUSL. Refer to the MPE Segmenter Reference Manual (30000-90011).

• By creating a new USL file with the BUILD command and specifying a file code of USL or 1024.

• By specifying a nonexistent uslfile parameter, thereby creating a permanent file of the correct size and type.

listfile

Actual file designator of the file on which the program listing is written. This can be any ASCII output file. Formal designator is BBCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BBCIN, BBCUSL, and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Examples

  BBASICOMP MYPROG,OBJECT

  BBASICOMP MYPROG

  PREPRUN $OLDPASS

Related Information

Commands

BBASIC, BBASICGO, BBASICPREP

Manuals

HP Business BASIC/XL Reference Manual
MPE Segmenter Reference Manual

BBASICPREP

Syntax

  BBASICPREP infile [,[progfile] [,listfile] ]

Parameters

infile

Actual file designator of the BSAVE file containing the HP Business BASIC/V program to be compiled. Formal file designator is BBCIN.

progfile

Actual file designator of the program file to which the prepared program segments are written. When progfile is omitted, the MPE segmenter creates the program file, which resides in the temporary file domain as $OLDPASS. If you do create your own program file, you must do so in one of two ways:

• By using the BUILD command and specifying a file code of 1029 or PROG and a numextents value of 1. This file is then used by the PREP command.

• By specifying a nonexistent file in the progfile parameter, in which case a temporary job file of the correct size and type is created.

listfile

Actual file designator of the file on which the program listing is written. This can be any ASCII output file. Formal file designator is BBCLIST. Default is $STDLIST.

NOTE: The formal file designators used in this command (BBCIN and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

Use

Example

  BBASICPREP MYCOMDS,MYPROG

Related Information

Commands

BBASIC, BBASICGO, BBASICOMP

Manuals

HP Business BASIC/XL Reference Manual
MPE Segmenter Reference Manual

BBXL

Syntax

  BBXL [commandfile] [,[inputfile] [,[listfile] ]] [;XL=xllist]

NOTE: This command follows the optional MPE/iX command line Syntax. Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.

Parameters

commandfile

The name of an ASCII file that contains a set of HP Business BASIC/XL commands and/or statements. The formal file designator is BASCOM. Default is $STDINX.

inputfile

Actual file designator of the file containing data input for a HP Business BASIC/XL program. Formal file designator is BASIN. Default is $STDINX.

listfile

Actual file designator of the destination file for the program listing and output. This can be any ASCII output file. Formal file designator is BASOUT. Default is $STDLIST.

xllist

A quoted list of the executable libraries which is searched when resolving external procedure references during execution of a user's program.

NOTE: The formal file designators used in this command (BASCOM, BASIN, and BASOUT) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

NOTE: This command is implemented as a command file. If you set the HPPATH variable to null (SETVAR ""), the command file is not executed and the command fails.

Use

Examples

  BBXL

  BBXL MYCOMDS,MYDATA,MYLIST

  BBXL XL='MYXL.MYGRP.MYACCT'

Related Information

Commands

BBXLCOMP, BBXLGO, BBXLLK

Manuals

HP Business BASIC/XL Migration Guide
HP Business BASIC/XL Reference Manual

BBXLCOMP

Syntax

  BBXLCOMP textfile [,[objectfile] [,listfile] ]

NOTE: This command follows the optional MPE/iX command line Syntax. Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.

Parameters

textfile

Actual file designator of the BASIC SAVE file (file code 1247 or BSVXL) containing the HP Business BASIC/XL program to be compiled. Formal file designator is BBCIN.

objectfile

Actual file designator of the object file to which the object code is written. This file is stored in binary form and has a file code of 1461 or NMOBJ. If your program uses GLOBAL COPTION RLFILE then this file is a binary file with a file code of 1033 or NMRL. Its formal file designator is BBCOBJ. If the objectfile parameter is omitted, the object code is saved to the temporary file $OLDPASS.

If you specify objectfile, the compiler stores the object file in a permanent file of the correct size and type, and with the name you specified.

For an NMOBJ file, if a file of the same name already exists, the object code overwrites that file.

For an NMRL file, if GLOBAL COPTION RLINIT is used, then the relocatable library file is overwritten. If GLOBAL COPTION RLINIT is not used, then the new object code is added but previously written information remains.

If the compiler issues an error message telling you that a new or existing object file is too small, build the object file with a larger size and recompile to it.

You may use the MPE/iX SAVE command to store $OLDPASS as a permanent file under another name.

listfile

The name of the file to which the compiler writes the program listing. This can be any ASCII file. The formal file designator is BBCLIST. If you do not specify listfile, the default is $STDLIST. $STDLIST is usually the terminal in a session or the printer in a batch job.

NOTE: The formal file designators used in this command (BBCIN, BBCOBJ, and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

NOTE: This command is implemented as a command file. If you set the HPPATH variable to null (SETVAR ""), the command file is not executed, and the command fails.

Use

Examples

  BBXLCOMP MYPROG,OBJECT

  BBXLCOMP MYPROG

  LINK
  RUN $OLDPASS

Related Information

Commands

BBXL, BBXLGO, BBXLLK

Manuals

HP Business BASIC/XL Migration Guide
HP Business BASIC/XL Reference Manual

BBXLGO

Syntax

  BBXLGO textfile [,[listfile] ] [;XL=xllist]

NOTE: This command follows the optional MPE/iX command line Syntax. Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.

Parameters

textfile

Actual file designator of the BASIC SAVE file (file code = 1247 or BSVXL) containing the HP Business BASIC/XL program to be compiled. Formal file designator is BBCIN.

listfile

Actual file designator of the file to which the program listing is written. This can be any ASCII output file. Formal file designator is BBCLIST. Default is $STDLIST.

xllist

A quoted list of the executable libraries which is searched when resolving external procedure references when the program is loaded.

NOTE: The formal file designators used in this command (BBCIN and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. Refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

NOTE: This command is implemented as a command file. If you set the HPPATH variable to null (SETVAR ""), the command file is not executed, and the command fails.

Use

Example

  BBXLGO MYPROG,LISTFL

Related Information

Commands

BBXL, BBXLCOMP, BBXLLK

Manuals

HP Business BASIC/XL Migration Guide
HP Business BASIC/XL Reference Manual

BBXLLK

Syntax

  BBXLLK textfile [,[progfile] [,listfile] ]

NOTE: This command follows the optional MPE/iX command line Syntax. Refer to "Optional Format for MPE/iX Commands" at the beginning of this chapter.

Parameters

textfile

Actual file designator of the BASIC SAVE file (filecode 1247 or BSVXL) containing the HP Business BASIC/XL program to be compiled. Formal file designator is BBCIN.

progfile

Actual file designator of the object file to which the Link Editor writes the linked program. If you do not specify progfile, the default is $NEWPASS, which is closed as $OLDPASS.

listfile

Actual file designator of the file on which the program listing is written. This can be any ASCII output file. Formal file designator is BBCLIST. If you do not specify listfile, the default is $STDLIST.

NOTE: The formal file designators used in this command (BBCIN and BBCLIST) cannot be backreferenced as actual file designators in the command parameter list. For further information, refer to the "Implicit FILE Commands for Subsystems" discussion of the FILE command.

Operation Notes

NOTE: This command is implemented as a command file. If you set the HPPATH variable to null (SETVAR ""), the command file is not executed, and the command fails.

Use

Example

  BBXLLK MYSCR,MYPROG

Related Information

Commands

BBXL, BBXLCOMP, BBXLGO

Manuals

HP Business BASIC/XL Migration Guide
HP Business BASIC/XL Reference Manual

BREAKJOB

Syntax

  BREAKJOB #Jnnn

Parameters

#Jnnn

A job number.

Operation Notes

Use

Examples

  BREAKJOB #J68

  SHOWJOB SUSP
  JOBNUM STATE INPRI JIN JLIST INTRODUCED JOB NAME
  #68   SUSP     105  LP  WED. 7:56AM TEST,USER.ACCT

Related Information

Commands

ALTJOB, ABORTJOB, RESUMEJOB, SHOWJOB, STREAM

Manuals

Performing System Operation Tasks

BUILD

Syntax

  BUILD filereferencer
    [;REC=[recsize][,[blockfactor][,[{F U V B}][,{BINARY | ASCII}]]]]
    [;{ CCTL | NOCCTL }]
    [ ;TEMP] [ ;DEV= [ dsdevice#  dsdevice#device [ device] ] ]
    [ ;CODE=filecode]
    [ ;DISC=[ [numrec] [,[numextents] [,initialloc]]]]
    [;{RIO | NORIO | MSG | CIR | STD | KSAMXL | SPOOL | KSAM64}]
    [ ;ULABEL=numlabels] [ ;KEY={ ^filereference keyinfo } ]
    [ ;FIRSTREC=recnum] [ ;REUSE ;NOREUSE ]
    [ ;langid={ langid langname } ]
    [ { ;DEFBLK ;OPTMBLK }]

Parameters

filereference

Actual name of the file to be created. The filereference can be either in MPE of HFS Syntax.

MPE Syntax

If the filereference does not begin with a dot or a slash, it is parsed according to the MPE Syntax and has the following format:

  filename[/lockword][.groupname[.acctname]]

MPE names must contain from one to eight alphanumeric characters, beginning with an alphabetic character. If acctname is specified, you must have create directory (CD) access to the target group in the account. The default groupname and acctname are the logon group and account.

HFS Syntax

If the filereference begins with a dot (.) or a slash (/), it is parsed according to the HFS Syntax. In this case the filereference can consist of 1 to 253 characters for relative pathnames (for example, ./253chars), and 254 characters for absolute names (for example, /254chars).

The following Syntax rules apply:

• File names are not upshifted.

• File names can be up to 254 characters in length for absolute pathnames, and 253 characters for relative pathnames.

• File names can begin with, and contain, any of the following characters:

  • a-z, A-Z, 0-9, _, .

• File names can contain (but not begin with ) a dash (-).

File names are of the form

   path/filename

where the path/filename combination may have a maximum of 255 characters.

recsize

Record size. A positive number indicates words, while a negative number indicates bytes for new files only. For fixed length files, this is the logical record size. For undefined length files, this is the maximum record size. For variable length files, this is the maximum logical record size if blockfactor is 1. If not, this is used to calculate the maximum logical record size and physical record size. For byte-stream files, recsize is 1 byte.

Records always begin on word boundaries. Therefore, the record size is rounded up to the nearest word boundary for block size calculations. For a binary file or a variable length ASCII file, odd byte lengths are rounded up and the extra byte is available for data.

However, if an odd byte length record size is specified for a fixed length or undefined length record file, the extra byte is not available for data. Default is the configured physical record width of the associated device. If you do not use the DEV= parameter, the default is DISC with 1023 records.

For example, a fixed length ASCII file with a record size specified as 11 bytes has only 11 bytes available for data in each logical record. However, to determine actual block size, 12 bytes is used for the record size (block size = 12 bytes multiplied by the blockfactor). If the file is specified as a binary file, the 11 bytes are rounded up to 12 bytes (6 words), all of which are available for each logical record.

blockfactor

The number of logical records per physical block in a new file. The default is calculated by dividing the specified recsize into the configured block size; this value is rounded downward to an integer that is never less than 1. For variable length record files, blockfactor and recsize are used to calculate the maximum logical and physical record size. The blockfactor is then set to 1. For files containing undefined length records, the blockfactor is ignored. The maximum size of blockfactor is 255.

For byte-stream files, blockfactor is set to 1.

F, U, V or B

Defines the length of the records of the file. A file may contain fixed length records (F), undefined length records (U), variable length records (V) or byte-stream format (B). For disk files, the default is F.

BINARY or ASCII

Indicates the type of records the file contains. BINARY indicates binary coded records and is the default. ASCII indicates ASCII coded records.

CCTL or NOCCTL

Indicates whether or not carriage control characters are supplied along with data written to an ASCII file. CCTL indicates carriage control characters accompany the data; NOCCTL indicates carriage control characters are not specified. The default is NOCCTL.

TEMP

Indicates that the file is created as a temporary file and is saved in the job/session temporary file domain when closed. The default is that a permanent file is created.

dsdevice

The device class name or logical device number used to open a communications link to a remote computer that contains the source file. The default is the local system, or the computer on which the transfer request originates. A # symbol is a delimiter between the file name of the remote computer and the remote device file name.

device

Either the devclass or ldev on which the file is to reside. A device class name (devclass), such as DISC consists of up to eight alphanumeric characters beginning with an alphabetic character. The DEV= parameter does not accept device names, volume classes, or volume names. When you specify devclass, the file is allocated to any available device in that class. If you are opening a file destined for a mountable volume, you must specify a device class that includes the drives upon which the home volume set is mounted. The file is then allocated to any of the home volume set's volumes that fall within that device class.

The logical device number (ldev) consists of a one to three number specifying a particular device. Default is the device class name DISC.

filecode

A code indicating a specially formatted file. This code is recorded in the file label and is available to processes accessing the file through the FFILEINFO or FGETINFO intrinsic. Although any user can specify a positive integer ranging from 0 to 32,767 or a mnemonic name for this parameter, certain reserved integers and mnemonics have particular system defined meanings.

Default is the unreserved file code of 0.

Using 1090 (LOG) as your designated file code may not yield the number of records you specify in the DISC= parameter. Most files use the number of records specified in the DISC= parameter as the maximum limit; user logging uses this specified number as a minimum.

numrec

The maximum number of logical records in a new file. The maximum for fixed length and undefined length records is 2,147,483,647. The default is 1023.

numextents

Maximum number of disk extents. You may specify a value of -1, or any number from 1 to 32. Default is 8.

initialloc

Number of extents to be initially allocated to the file at the time that it is opened. If you specify -1 for this parameter, the default value is used.

RIO or NORIO

RIO creates a relative I/O file, which is a special file access method primarily used by COBOLII programs. You can, however, access these files from programs written in any language. Specifying RIO implicitly changes the record length parameter to F, or fixed length record. The default, NORIO, creates a nonrelative I/O file.

RIO and NORIO specifications affect only the physical characteristics of the file. If NOBUF is specified in the FILE command, the file is not accessed in RIO mode; otherwise, RIO access is used with RIO files. Special operations on RIO files, such as replicating an RIO file, set NOBUF access. Refer to the Accessing Files Programmer's Guide for a discussion of relative I/O.

STD, MSG, CIR, KSAMXL, SPOOL, KSAM64

Defines the type of file.

The default is STD (standard MPE/iX disk file). You do not need to specify STD; in fact, if you do specify it, you will see the error message The STD keyword is not appropriate in the context of a BUILD command. (CIERR 216).

A MSG (message file) allows communication between any set of processes in a first in, first out (FIFO) manner. Records are read from the start of the file and are logically deleted and/or are appended to the end of the file.

CIR (circular file) acts as a normal sequential file until full. When full, the first physical block is deleted when the next record is written, and remaining blocks are logically shifted to the front of the file. A circular file cannot be simultaneously accessed by readers and writers.

KSAMXL specifies a native mode KSAM file (KSAM XL file).

SPOOL specifies an unlinked output spool file. The default outpri on the spool file is 8; the default number of copies is 1. The unlinked output spool file must be created on a disk device. Specify the target printer device at SPOOLF...;PRINT time; if you do not, an error results.

The characteristics of a file created with the SPOOL keyword are:

• variable length records of 1008 bytes each

• a blocking factor of 1

• ASCII format

• permanent file

• record limit of 1023

• undefined maximum number of extents with 0 extents initially allocated

KSAM64 specifies a KSAM file that is capable of holding more than 4GB of data. KSAM64 files are compatible in every other way with KSAM XL files. All options that apply to KSAM XL files also apply to KSAM64 files.

These characteristics override any other characteristics, such as binary format, which may be specified.

numlabels

The number of user label records to be created for the new file. Up to 255 labels can be specified. This parameter applies to any type of file.

^filereference or keyinfo

filereference is a file containing key information. This parameter only applies to new KSAM files; it is required for new KSAM files. The caret (^) indicates that the contents of the file will be used.

keyinfo has the following format:

  ;KEY=
   (keytype,keylocation,keysize
    [,DUP|RDUP];
       .
       .
    keytype,keylocation,keysize
    [,DUP|RDUP])

One key specification (keytype, keylocation, keysize [,DUP|RDUP] must be included for each key in the KSAM file. The first occurrence of the key specification describes the primary key; each subsequent key specification describes an alternate key. There may be up to 15 alternate key specifications in addition to the primary key description.

keytype

KSAM key type, specified as BYTE, INTEGER, REAL, IEEEREAL, NUMERIC, PACKED, OR *PACKED. Specify the whole word or only the first letter; valid abbreviations are B, I, R, E, N, P, and *. If more than one letter is specified, the word must be spelled correctly.

keylocation

Location of the first byte of the key within the data record counting from the first byte in the record. The first byte in the data record is always numbered 1. Only one key can start at the same location. This parameter applies only to KSAM files.

keysize

Length of the KSAM key in bytes. The length depends on keytype as follows:

  BYTE       1 to 255 bytes
  INTEGER    1 to 255 bytes
  REAL       1 to 255 bytes
  IEEEREAL   4, 8, or 16 bytes
  NUMERIC    1 to 28 bytes
  PACKED     1 to 14 bytes (odd number of digits)
  *PACKED    2 to 14 bytes (even number of digits)

This parameter is required for all key types.

DUP OR RDUP

These two options apply only to KSAM files. The DUP option allows you to specify that duplicate key values are permitted. If DUP is not specified, records with duplicate key values are rejected and an error message is issued when such records are written to the file. When the DUP option is used, each new duplicate key is inserted at the end of the duplicate key chain. This maintains the chronological order of the duplicate keys.

The RDUP option specifies that duplicate keys are allowed and to be inserted randomly in the duplicate key chain. This method makes insertion of such keys faster, but does not maintain the chronological order of the duplicate key chain. The default is that duplicate keys are not allowed.

recnum

Determines whether record numbers in the new KSAM file are to start with zero or one. If the integer 1 is specified, records are numbered beginning with 1; otherwise, they start with 0. The only acceptable values for recnum are 1 and 0. This option can only be used for new KSAM files.

REUSE or NOREUSE

The REUSE option forces KSAM files to reuse deleted record space. The REUSE option forces RDUP to be set to TRUE for all keys.

If the NOREUSE option is used, deleted record space is not reused. If the DUP option is specified for a key, duplicate records are placed chronologically at the tail end of the file. The default is NOREUSE.

langid

An integer number indicating the native language of the KSAM file to be built. The default is 0, or NATIVE-3000. The language must be currently configured on the system. See the Native Language documentation for more information.

langname

The name indicating the native language for the KSAM file to be built. The default language is NATIVE-3000. The language must be currently configured on the system. See the Native Language documentation for more information.

DEFBLK or OPTMBLK

These two options apply only to KSAM files. DEFBLK specifies that the data block size will be the default data block size of 4096 bytes. OPTMBLK specifies that the OS will select the optional data block size based on the record size. The default is DEFBLK.

NOTE: The file system uses the values specified on the BUILD command line to compute other characteristics of the file. Therefore, the values (or default values) may be valid within their respective fields, but may cause overflow errors in the computation of internally needed file specifications.

Operation Notes

  BUILD filename;REC=128,1,F,BINARY;DEV=DISC;DISC=1023,8,

Use

Examples

  BUILD WORKFILE;REC=-80,3,F,ASCII;DISC=2000,10,2

  BUILD NEWDATA;DISC=3000,1,1;CODE=LOG

Related Information

Commands

COPY, LISTFILE, LISTF, LISTFTEMP, PURGE, RENAME

Manuals

MPE/iX Intrinsics Reference Manual
Native Mode Spooler Reference Manual

BYE

Syntax

  BYE

Parameters

Operation Notes

  CPU=48. CONNECT=35. FRI, MAY 4, 1987, 10:56 PM

Use

Example

  BYE

Related Information

Commands

HELLO

Manuals

None