Edit strings can be specified in various parts of the REPORT system. The standard edit string elements are listed below. There are three basic types of edit operands:

1. Numeric fields
2. Alphanumeric fields
3. Date fields

Each type has its own edit string elements. To repeat an edit string element, append to the string element character. the number of instances of that character, with the number bracketed by parentheses. For example, to print an alphanumeric field of 5 characters use "X(5)" instead of "XXXXX". The various types are detailed in the following charts.

Numeric String	Description
9	Each 9 is replaced with a digit 0 through 9. The number is right justified and leading zeros are added.
Z	If a Z matches a leading zero in the field's contents, it is replaced by a space. If not, it is replaced with a digit 0 through 9.
+	A plus sign is replaced by either a plus sign if the contents are positive or a minus sign if it is negative. If more than one plus sign is placed leftmost, any leading zeros are suppressed and the sign floats over to the right.
L	A L placed at the left of an edit string will cause the field to be left justified.
-	A minus sign is replace with a blank if the fields contents are positive and a minus sign if it is negative. If more then one minus sign is placed leftmost, any leading zeros are suppressed and the sign floats over to the right.
.	A period represents the decimal point placement. It is replaced by the current radix point symbol. A period is the default radix symbol. The radix symbol is defined by the logical name SYS$RADIX_POINT. Put only one decimal point in a numeric string.
,	A comma is the digit separator. If all digits at the left are suppressed zeros, then the comma is replaced by blank. Otherwise it is replaced with the current digit separator symbol. A comma is the default digit separator. The digit separator symbol is defined by the logical name SYS$DIGIT_SEP.
B	The letter B is replaced by a blank at that position.
$	A $ is replaced by the current currency symbol. The default currency symbol is $. The currency symbol is defined by the logical name SYS$CURRENCY. If more than one currency symbol is placed leftmost, any leading zeros are suppressed and the symbol floats over to the right.
CR	If the field's contents are negative, the letters CR are inserted. In all other cases, 2 blanks are inserted.
DB	If the field's contents are negative, the letters DB are inserted. In all other cases, 2 blanks are inserted.
W	Force a period decimal point.

Alphanumeric String	Description
A	Each A is replaced by an alphabetic character or an asterisk.
9	Each 9 is replaced by an numeric character or an asterisk.
B	Each B is replaced by a blank.
X	Any alpha character is acceptable.
T	Any alpha character is acceptable.
W	Expand the string until entire input string fits. The increment used is the number of W's found. Must be the rightmost characters

Date String	Description
A	Each A is replaced by an alphabetic character from the field's contents. All others are replaced with an asterisk.
B	The letter B is replaced by a blank at that position.
D	Each D is replaced by the corresponding digit of the day of the month. DD is recommended.
E	Each E is replaced by the corresponding digit of the day of the month. Includes leading blanks.
F	Each F is replaced by the corresponding digit of the day of the month. Includes leading zeros.
J	Each J is replaced by the corresponding digit of the Julian date. JJJ is recommended.
L	A L placed at the left of an edit string will cause the field to be left justified.
M	Each M is replaced by the corresponding letter of the name of the month. An edit string of M(9) prints the entire name of the month.
N	Each N is replaced by a digit of the number of the month. NN is recommended.
O	Each O is replaced by a digit of the number of the month. Skip leading blanks.
Q	Each Q is replaced by a digit of the number of the month. Including leading zeros.
P	P for PM. Nothing for AM.
U	Time of day using 12 hour clock.
Y	Each Y is replaced by the corresponding digit of numeric year. YY or YYYY is recommended.
T	Each T is replaced by a character of the time. The time is displayed as HH:MM:SS.DD.
W	Each W is replaced by the corresponding letter from the name of the day of the week. An edit W(9) prints the entire name.
X	Each X is replaced by one character from the SYS$ASCTIM representation of the date
,	A comma will be inserted at that position.
.	A period will be inserted at that position.
-	A dash will be inserted at that position
/	A slash will be inserted at that position.

The CONTROL file contains several record types. The primary one is the SDE record which is documented below. The others are directory definitions and list specification, and these are not suitable for external use.

Whenever a new job is created a new CONTROL record is made. A new record is first loaded with a set of default values before user specified values are loaded. If the job entry called "/default/default" is found, that is used as the initial default. Otherwise a series of hard values are used.

The general description of all fields in the CONTROL file are listed below:

• SUBMIT OPTIONS: All the various submit parameters below only apply to the batch job that is created when execution is requested. They are not used to control any other facet of the SCHEDULE system. For more information on what these do please refer to the bg command description.
  • USER: All automated submit operations are done on the behalf of this user. Only a user with CMKRNL can change this field.
  • CLI: The CLI field specifies which command language interpreter that will be enabled for the job.
  • NODE: The NODE field specifies on which node this job is to execute. Inside a cluster any node that is a member of the same cluster is allowed to submit and execute the job. This parameter is very useful in a "Satellite/Central database" ¹ Satellite/Central database. 2) Peer-to-Peer systems. )
    network configuration. In this network topology the job will execute on the remote node. All the control data and commands will come from the central database.
  • CHARACTERISTIC: The CHARACTERISTIC field is a single known characteristic name that is to be associated with the job when it is submitted. Characteristics are arbitrary attributes that can be assigned to job queues. A job will only execute in a queue with matching characteristics.
  • CPUTIME: The CPUTIME field specifies the maximum CPU time that the job will execute. If the batch queue also has a CPU time limit the smaller of the two is used. If none is specified this implies NO LIMIT.
  • FLAGS: The submit flags are HOLD, KEEP, PRINT and DELETE. These flags are the standard flags and they have the following meanings.
    1. HOLD - Place the job in the PENDING state on entering into the batch queue.
    2. KEEP - Keep the log file on line after the job finishes.
    3. PRINT - Print the log file after the job completes.
    4. DELETE - Delete the job temporary file on completion.
    
    
  • LOG_FILE: The LOG FILE field specifies where to place the job log file that is created during job execution. Any file name that is provided is parsed and a default of "/job_name.LOG" is used to complete any missing elements.
  • PRINTER: The PRINTER field defines what print queue that the log file, if it is to be printed, is to be inserted into. The default if none has been defined either implicitly or explicitly is SYS$PRINT.
  • NAME: The NAME field defines the job name that is to be assigned this job when it is in the batch execution queue. This name will only appear when you use the VMS command SHOW ENTRY or SHOW QUEUE. By default this name is the same as the job entry in the SCHEDULE database.
  • PARAMETER: The PARAMETER fields (P1 through P8) are just character data They can be used in what ever fashion is needed by the developer.
  • PRIORITY: The PRIORITY field specifies what queue priority to assign this job when it is inserted into the batch queue for execution. A non-privileged user is limited to a maximum value that is controlled by the AUTHORIZE program and/or the SYSGEN parameter MAXQUEPRI. The priority is NOT the execution priority but strictly the priority used to order jobs in the batch execution queue while they are waiting to start.
  • ACCOUNT: The ACCOUNT field specifies what account value to assign the job when it is submitted for execution. This parameter is only useful if you have an application that can use this value.
  • WSDEFAULT: The WSDEFAULT field defines for a batch job a working set default, the default number of physical pages that the job can use. If the queue on which the job executes has a nonzero default working set, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set default of 0, the smaller of the specified job and UAF values (value established in the user authorization file) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. Working set default values must range between the numbers specified by the SYSGEN parameters PQL_MWSDEFAULT and WSMAX.
  • WSEXTENT: The WSEXTENT field defines for the batch job a working set extent, the maximum amount of physical memory that the job can use. The job uses the maximum amount of physical memory only when the system has excess free pages. If the queue on which the job executes has a nonzero working set extent, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set extent of 0, the smaller of the specified job and the value established in the user authorization file (UAF) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. Working set extent values must range between the numbers specified by the SYSGEN parameters PQL_MWSEXTENT and WSMAX.
  • WSQUOTA: The WSQUOTA field defines for the batch job a working set quota, the amount of physical memory that the job is guaranteed. If the queue on which the job executes has a nonzero working set quota, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set quota of 0, the smaller of the specified job or the value established in the user authorization file (UAF) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. Working set quota values must range between the numbers specified by the SYSGEN parameters PQL_MWSQUOTA and WSMAX.
  
  
• NOTIFICATION OPTIONS: Whenever a notification event occurs the information regarding the event is collected and place in a temporary COM file. This file is then submitted to the notification batch queue indicated in the system parameter file. This notification procedure ² parameter in the parameter file.) is capable of delivering two types of messages. One is a broadcast message to the user (if still logged in). The other is a mail message. The user name or names that are specified can be logical names that in turn provide a distribution list for all the various messages.
  The various notification events are detailed below: "."
  1. SUBMITTED: This field indicates that the user(s) is to receive a message when the job has been submited for execution.
  2. STARTED: This field indicates that the user(s) is to receive a message when the job actually starts execution.
  3. DELAYED: This field indicates that the user(s) is to receive a message when the job has been delayed. A job is considered delayed if it stays in a "wait for" scheduling queue longer then the AFTER_DELAYED time. In all the other scheduling queues a job is considered delayed if it stays there longer then the value indicated by the STUCK_AFTER parameter.
  4. COMPLETED: This field indicates that the user(s) is to receive a message when the job has completed successfully.
  5. FAILED: This field indicates that the user(s) is to receive a message when the job fails. During the processing of scheduling requests various problems can arise (for example invalid calendar name, etc.). All such events are also trigger failure notification events.
  6. AFTER_DELAYED: This field indicates the interval after which a job is considered delayed.
  
  
• RESOURCE REQUIREMENTS: Two types of resource requirements can be imposed on a job. Both requirements must be met before a job is submitted for execution. Two sets of resource used information are collected. These parameters are detailed below: "."
  1. DISK_SPACE: The DISK SPACE field indicates how much disk space must be available on a certain disk before this job is to start. The job will wait in the scheduling queue "wait for disk space" until such time that this amount of space becomes available.
  2. FILE: The FILE field indicates that a certain file must be present for the job to proceed. The job will wait in the scheduling queue "wait for file" until such time that this file becomes available.
  3. MEASURED: As each job completes the usage information is collected and add in to the average usage statics. The following four numbers are maintained. "-"
     1. CPU TIME: The average number of seconds for CPU time used by the job.
     2. ELAPSE TIME: The average number of seconds of wall clock time used by the job.
     3. IO COUNT: The average number of I/O's (buffer I/O plus direct I/O) that the job uses.
     4. COUNT: The number of runs that this average is computed over.
     
     
  4. ESTIMATED: Each job can be provided an estimated usage value. These numbers are not changed by the system and are there to provided an additional slot to store planned or estimated values. The following fields are provided. "-"
     1. CPU TIME: An estimated CPU time in seconds.
     2. ELAPSE TIME: An estimated elapse time in seconds.
     3. IO COUNT: An estimated I/O count for the job.
     
     
  
  
• GENERAL INFORMATION: Each job contains a group of general information describing the job, access to job and when the job is to start.
  1. COMMENT: The COMMENT field is just a text field into which any data can be inserted.
  2. NEXT_SUBMIT: The NEXT_SUBMIT data is the next time the job will automatically start. Any that job that is to start (without being manually started) must have a start time set. Once the start time has occurred and the job submitted for execution then the reschedule parameters are used to determine how to reset this date to the next start time.
  3. LAST_START: The LAST_START time is an output field that is updated whenever the job has been submitted and is starting to execute.
  4. LAST_SUBMIT: The LAST_SUBMIT time is an output field that is updated whenever the job is submitted into a batch queue for execution.
  5. LAST_COMPLETED: The LAST_COMPLETED time is an output field that is updated whenever a job completes, either success or failure.
  6. RESTART_COUNT: The RESTART_COUNT field indicates how many times a job is allowed to be automatically restarted. A non-zero value indicates that the job can be restarted on failure (error and severe error conditions) and how many times it is allowed. Any initiate jobs that are specified are not activated until a job has failed this number of times. Detected job failure events include such things as a node going down, a job explicitly deleted out of the queue or a program failure.
  7. UP_COUNT: The UP_COUNT field is incremented each time a job is submitted for execution.
  8. DOWN_COUNT: The DOWN_COUNT field is decremented each time a job submitted for execution. When a value of zero is reached all automatic job submissions terminate. A value of INFINITE or -1 indicates an unlimited number of runs are allowed.
  9. OWNER: The owner field indicates the UIC that controls the job. This can be either an IDENTIFIER or a UIC code.
  10. PROTECTION: The protection field is a bitmap that grants access to the system, owner, group and world classes. The protection bits are used as follows:
      1. D - Delete access allowed to the job
      2. W - Write access allowed to the job
      3. R - Read access allowed to the job
      4. E - submit, initiate or prerequisite access allowed
      
      The access modes are nested as follows:

      D -> W -> R -> E

      
      In other words W access gives you W, R and E access but not D.

  11. ACL: Each job can have an Access Control List associated with it. An ACL is a list of identifiers and what access each one of thus identifiers can obtain. The rules for ACL formating are the standard VMS ones. Please refer to the VMS documentation for more information.
  12. FLAGS: Only one general job flag exists at this time. A flag value of NOHISTORY indicates that no history information is to be accumulated for this job.
  13. STATUS: The STATUS field is an output field and indicates the last completion status code that was generated by the job.
  14. JOB_TAG: The JOB_TAG field is the initial value that is given the SET_TAG whenever this job is used to start a job set.
  15. PRE_COM_FILE: The PRE_COM_FILE is a command procedure that is executed first before any other DCL commands associated with a job.
  16. POST_COM_FILE: The POST_COM_FILE is a command procedure that is executed last after all DCL commands associated with the job.
  17. STARTUP_WINDOW: The STARTUP_WINDOW is used to control how jobs that are in the B (waiting until start time) scheduling queue are processed when the system is booted. In a cluster this would be when all nodes go down and come up. When the system comes up a check is made to see if any jobs in the B queue should have already been started. If so and that start time is no more then the STARTUP_WINDOW in the past the job is initiated. The main purpose is to prevent extra job starts if the system has been down for a long time.
  18. EXECUTE_WINDOW: The EXECUTE_WINDOW is maximum time that is allowed for a job to go from the E (waiting for prerequisites) to the M (job completed) scheduling queue. If this limit is exceeded any initiate jobs are not activated. If a job is already in an execution queue the batch job is allowed to terminate. The main purpose is to prevent a run away catch up mode from taking place if the system comes back up after being down for a long time. This condition is checked in the scheduling queues H, I, J and M.
  
  
• RESCHEDULING OPTIONS: Jobs that have time based starts can be rescheduled via one of three methods. The various methods are detailed below:
  1. INTERVAL Rescheduling: Interval rescheduling uses the current start time and just adds in the interval to determine what the next start time should be.
  2. MARKED CALENDAR Rescheduling: Marked calendar rescheduling looks for a specified mark (a letter A through Z) on the indicated calendar and then runs the job at the indicated time of day.
  3. NAMED DAY Rescheduling: Named day rescheduling selects the next run date by the name of the day (MONDAY, TUESDAY, etc.) and then runs the job at the indicated time of day.
  4. CALENDAR: This field indicates what calendar to use when determining the next start time. For example, what days are holidays and weekends is determined by examining the calendar.
  5. NONE: This option clears out all automatic job rescheduling.