Home >
Hercules >
HASP V4 >
HASPGEN Parameters
&APGPRTY
In an OS/VS2 Release 1 environment, defines the priority level
of the Automatic Priority Group.
&APGPRTY=7
This parameter is used in conjunction with related parameters
&PRI(n).
If a job is initiated under a HASP logical initiator n whose
&PRI(n)
is equal to &APGPRTY, then HASP will remove DPRTY= parameters from EXEC
statements of the job.
&AUTORDR
Specifies the inclusion or exclusion of code in HASP to recognize
automatically when a card reader available to HASP becomes ready.
Acceptable values are YES (include the code) and NO (exclude the code).
&AUTORDR=YES
If &AUTORDR is specified as NO, HASP card readers remain INACTIVE when
they become ready; a $SRDRnn command must be issued to make HASP begin
reading cards. With &AUTORDR=YES, HASP begins reading cards automatically
when the reader is made ready, much like JES2 Release 4.1 does when it
is the primary subsystem.
&BSCCPU
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for HASP MULTI-LEAVING Remote Job Entry.
&BSCCPU=NO
&BSC2770
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for the 2770 Data Communication System.
&BSC2770=NO
&BSC2780
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for the 2780 Data Transmission Terminal.
&BSC2780=NO
&BSC3780
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for the 3780 Data Communication System.
&BSC3780=NO
&BSHPRES
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for the Space Compression/Expansion feature
of 2770 and 3780 terminals.
&BSHPRES=NO
- This support must be included if any 2770 or 3780 terminal
will transmit to HASP using the Space Compression/Expansion feature.
- Use of this support for any specific terminal is controlled by
specification in the RMTnn parameter for the
terminal.
&BSHPRSU
Specifies inclusion (YES) or exclusion (NO) of the HASP Remote Job Entry
Printer Interrupt feature for binary synchronous hardware terminals.
If this feature is included, the remote terminal operator may interrupt
printing to transmit jobs or HASP commands to HASP.
&BSHPRSU=YES
&BSHTAB
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of support for the Printer Horizontal Format Control feature
of 2770, 2780 and 3780 terminals.
&BSHTAB=YES
Use of this support for output to any specific 2770, 2780 or 3780
terminal is controlled by specification in the
RMTnn
parameter for the terminal.
$BSPACE
Specifies the character that will be interpreted as the System/370
hardware-defined backspace character X'16'. When the $BSPACE
character is entered, it will be removed from the command text,
along with the previously entered character (if any). Characters
following the $BSPACE character will be shifted left to replace
the characters that have been removed. $BSPACE is specified using
the two hexadecimal digit representation of the EBCDIC character.
$BSPACE=5F (the EBCDIC "not" sign)
$BSPACE does not apply to commands entered from any sources other
than operator consoles.
&BSVBOPT
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of code to recognize an EM (end of media) punch in card
images nontransparently by the 2780 Data Transmission Terminal.
&BSVBOPT=NO
&BUFSIZE
Specifies the size in bytes of each HASP buffer. If the value specified
is not a multiple of eight, it will be adjusted upward to a multiple of
eight. &BUFSIZE must be an integer not larger than 4008 and not smaller
than (400+
&NUMDA*
&NUMTGV/8).
&BUFSIZE=1960
- &BUFSIZE must be 536 or greater if HASP will drive 3211 printers.
- The maximum number of /*OUTPUT control cards allowed per job is
calculated as ((&BUFSIZE-4)/32).
$CKPTIME
Specifies the interval, in seconds, at which selected HASP information
will be checkpointed for warm start.
$CKPTIME=60
The time interval specified for $CKPTIME is taken as a maximum. Checkpoints
are also taken when a job changes its status in the HASP job queue.
&CLS(n)
Subscripted variable symbols &CLS(n) specify HASP job classes. The nth
HASP logical partition may select, for OS execution, a job from the HASP
job queue, only if the job's class (specified by the user or defaulted to A)
specified in the &CLS(n) parameter or specified by the operator in a
"$TImm,list" command for the logical partition, where mm=
&PID(n).
Each specification must be a 1- to 53-character string of valid HASP job classes.
The same HASP job class may appear in two or more specifications.
&CLS(1)=A |
&CLS(2)=BA |
&CLS(3)=CBA |
&CLS(4)=DCBA |
- Only the first &MAXPART specifications,
&CLS(1) through &CLS(&MAXPART), will
be used.
- If &MAXCLAS is specified as less than 53, a maximum of
&MAXCLAS characters should be specified for each value.
&DEBUG
Specifies inclusion (YES) or exclusion (NO) of debugging code in the
generated HASP system.
&DEBUG=NO
The &DEBUG option is independent of the
&TRACE option.
$DELAYTM
Specifies a delay time in microseconds to be applied by the HASP Remote
Terminal Access Method when transmitting to either MULTI-LEAVING System/360
Model 20, Submodel 2, 4, or 6, or to a 2922 remote terminal over a 19,200
baud or greater teleprocessing line.
$DELAYTM=100
If data overrun line errors occur at the workstation with the default
value, the value should be increased to minimize such errors.
&DMNDSET
Specifies whether inline printer setup will be allowed (YES) or not allowed
(NO) for data sets whose SYSOUT class matches the job message class.
&DMNDSET=YES
- If &DMNDSET=YES, all SYSOUT data sets whose class matches the message
class will be printed on one printer, with appropriate setup messages to
the operator as the data sets are printed.
- If &DMNDSET=NO or if SYSOUT class does not match the message class,
separate work elements will be created for each unique setup required.
In this case, data sets can be printed simultaneously on all available
printers.
$ESTIME
Specifies the default estimated execution time, in minutes, for a job.
The specified value must be an integer greater than zero.
$ESTIME=2
If a user does not specify a value for estimated execution time, in the
accounting field of his JOB card or on a /*JOBPARM statement, the value
of $ESTIME is used.
$ESTLNCT
Specifies the default estimated print line count, in thousands of lines,
for a job. The specified value must be an integer greater than zero.
$ESTLNCT=2
If a user does not specify a value for estimated print line count, in the
accounting field of his JOB card or on a /*JOBPARM statement, the value of
$ESTLNCT is used.
$ESTPUN
Specifies the default estimated punched card count, in cards, for a
job. The specified value must be an integer greater than zero.
$ESTPUN=100
If a user does not specify a value for estimated card count, in the
accounting field of his JOB card or on a /*JOBPARM statement, the value of
$ESTPUN is used.
&FCBV
Specifies inclusion (YES) or exclusion (NO) of 3211 Variable Forms
Control Buffer loading compatibility. If set to YES, the "V" specified
FCB image is generated and the code to support the $TF... command is
included.
&FCBV=NO
&JCOPYLM
Specifies the maximum allowable value for job output copies requested in
the JOB card accounting field or on the /*JOBPARM card. The value specified
must be an integer between 1 and 255 inclusive.
&JCOPYLM=3
- If the number of job copies requested is greater than &JCOPYLM, the
request will be reduced to &JCOPYLM. No error message will be produced.
- The setting of this parameter does not affect requests for multiple
copies of data sets vial the /*OUTPUT card.
$LINECT
Specifies the default maximum number of lines to be printed per page of a
job's printed output.
$LINECT=61
- If a user does not specify a value for line count, in the accounting
field of his JOB card or on a /*JOBPARM card, the value of $LINECT is used.
- Setting $LINECT=0 will cause automatic page overflow (normally provided
by HASP) to be suppressed unless overridden by the JOB card accounting
parameter or /*JOBPARM controls statement specification.
LINEmm
LINEmm statements specify the characteristics of teleprocessing lines to be
used by HASP Remote Job Entry. Lines must be defined consecutively,
starting with LINE01. Each specification must be a 5-character string
of the form:
where the letters represent the following:
Code Letters
|
Range
|
Description |
mm | 01-99 | Line number |
aaa | 000-FFF | BSC adapter address (see Note 2) |
l | 0-5 | Line descriptions as follows: |
| | 0 = Interface A - half-duplex (1200-9600 baud) |
| | 1 = Interface A - full-duplex (1200-9600 baud) |
| | 2 = Interface A - full-duplex (19.2-230.4 k-baud) |
| | 3 = Interface B - half-duplex (1200-9600 baud) |
| | 4 = Interface B - full-duplex (1200-9600 baud) |
| | 5 = Interface B - full-duplex (19.2-230.4 k-baud) |
c | 0-7 | Code as follows: |
| | 0 = Code A - EBCDIC - no transparency |
| | 1 = Code A - EBCDIC - transparency |
| | 2 = Code A - USASCII - no transparency |
| | 3 = Code A - USASCII - transparency |
| | 4 = Code B - EBCDIC - no transparency |
| | 5 = Code B - EBCDIC - transparency |
| | 6 = Code B - USASCII - no transparency |
| | 7 = Code B - USASCII - transparency |
LINEmm=***01
- Parameter &NUMLNES must specify the number of
LINEmm specifications to be included in the generated HASP system.
- The unit address aaa may be specified as ***. HASP initialization
will assign unit addresses to lines whose unit addresses are specified
as *** by scanning the OS UCBs. A teleprocessing UCB whose device type
field specifies a 2701 BSC Adapter or a 2703 BSC Adapter will be recognized
as a UCB defining a line. If the unit address of such a UCB is not
specified explicitly in any of the first &NUMLNES
line definitions LINEmm, HASP initialization will assign the UCB
to the first line number whose unit address is specified ***
and will change the *** to the EBCDIC address specified in
the UCB. However, if no line definition remains whose unit
address is ***, HASP will not use the line.
- If a line specification LINEmm designates USASCII, that line
cannot be used with any but 2770, 2780, or 3780 USASCII terminals.
HASP will translate each record it receives into EBCDIC, and each
record it transmits into USASCII before transmission. See also
HASPGEN parameter &USASCII.
- Interface B and Code B refer to the second code or interface
in a BSC Adapter with the Dual Communications Interface and/or
Dual Code special feature(s).
- The same unit address aaa may be specified in more than one
LINEmm definition to allow use of different interfaces or
codes available in a single BSC Adapter. HASP will allow
only one such LINEmm to be started by the operator at any one
time.
&LOGOPT
Specifies inclusion (YES) or exclusion (NO) of code to support the HASP
Job Log.
&LOGOPT=YES
- The HASP Job Log contains console messages and replies to WTORs
issued during processing of the job.
- If &LOGOPT=YES, the HASP Job Log may be suppressed on an individual job
basis via a parameter in the accounting field of the JOB card or via a
parameter on the /*JOBPARM control statement.
- If the HASP Job Log is suppressed, the HASP statistics information,
normally printed with the job, is also suppressed.
&LONGCOM
Specifies whether the alternate long form of HASP commands is available (YES)
or unavailable (NO) to the operator.
&LONGCOM=NO
&MAXCLAS
Specifies the maximum number of job classes which may be specified via the
HASP operator command "$TIn,list" for a HASP logical partition. The value
must be an integer from 1 to 64 inclusive.
&MAXCLAS=8
No more then &MAXCLAS characters may be specified for each of the
parameters
&CLS(n).
&MAXJOBS
Specifies the maximum number of job that can be in the HASP system at any
one time. The value must be an integer greater than zero.
&MAXJOBS=100
- This variable does not affect the range of HASP job numbers, which is
always 1 to 9999.
- The value of &MAXJOBS strongly influences the size of the first and
second HASP checkpoint records. The size of the first checkpoint record
is:
The size of the second checkpoint record is:
If any checkpoint record is longer than the track size of the device on
which the primary SPOOL volume is mounted, HASP will not operate correctly.
&MAXPART
Specifies the number of HASP logical partitions to be defined. The value
must be an integer between 1 and 63 inclusive.
&MAXXEQS
Specifies the maximum number of jobs that may concurrently be active in the
HASP execution phase. The value must be an integer greater than zero.
&MAXXEQS=3
See also
&MAXPART, the variable that determines
the number of HASP logical partitions.
&MINBUF
Specifies a minimum threshold of HASP buffers below which a warning
message is produced. The specification should be an integer value,
representing the minimum number of buffers determined necessary for
the installation (see
&NUMBUF).
- HASP will automatically attempt to utilize, via variable GETMAIN, any free
space in its region as additional buffers. If the number of buffers added to
the variable &NUMBUF is less than the value of
&MINBUF, the warning message:
will be issued during HASP initialization, and processing will continue.
- Because changes in HASPGEN options, local modifications and/or OS can
affect the number of HASP buffers, proper setting of this variable can prevent
a possible undetected performance degradation.
- See the description of HASPGEN parameters &NUMBUF
and &RESCORE for related information.
&MINJOES
Specifies the lower bound for the number of free Job Output Elements.
When the free count drops below &MINJOES, no new work still be added
to the in-storage queues until print or punch activity raises the free count.
the installation (see
&NUMBUF).
If the Job Output Element free count is allowed to go to zero, there will be
no way to support the $I and $N operator commands for printers or punches.
&MLBFSIZ
Specifies the size in bytes of each HASP MULTI-LEAVING buffer. The value
must be a positive integer no greater than
&TPBFSIZ.
&MLBFSIZ=400
- The value specified for &MLBFSIZ automatically becomes the MULTI-LEAVING
buffer size in each HASP MULTI-LEAVING Remote Terminal program.
- Satisfactory support of one device of each type (reader, printer, punch,
console) on 8K terminal CPUs is based on the assumption that &MLBFSIZ is 400
or less. If the supported terminals include any 8K CPUs, it is recommended
that &MLBFSIZ not be increased above 400, even if support for a nonprogrammable
terminal requires increasing &TPBFSIZ to 516.
&NUMBUF
Specifies the number of input/output buffers to be included in the HASP load
module. It should normally be set to reflect the total number of buffers
required for proper operation of HASP. However, because HASP will automatically
use free space in its region to dynamically construct additional buffers, there
are circumstances when &NUMBUF may be set to a value less than the actual
number of buffers required for proper HASP operation. In this case, it is
assumed that sufficient additional buffers will be dynamically obtained from
free space in the HASP region to provide an adequate total number of buffers
(see
&MINBUF and
&RESCORE).
&NUMBUF=15
- The following list indicates the number of buffers required for each
logical function. A defined function that is inactive requires no buffers.
- 3 for each local input function
- 2 for each internal reader
- 2 for each remote input function
- 2 for each local print function (1 if $PRTBOPT=1)
- 1 for each remote print function (2 if $RPRBOPT=2)
- 1 for each local punch function (2 if $PUNBOPT=2)
- 1 for each remote punch function (2 if $RPUBOPT=2)
- 3 for each OS job execution (minimum value)
For performance reasons, additional buffers must be available to sustain
periods of high SYSIN/SYSOUT activity by jobs being processed by OS.
Additional buffers beyond the requirements described above should be
included corresponding to the value:
Severe performance and/or device degradation can occur in a system that
contains insufficient buffers to perform required functions.
- To avoid a complete system failure caused by a buffer lockout condition,
the number of available buffers must never be less than the value:
&NUMCLAS
Specifies the maximum number of classes that a printer may simultaneously
select. Because there are 36 unique SYSOUT classes, the maximum allowable
value of &NUMCLAS is 36.
&NUMCLAS=8
&NUMDA
Specifies the maximum number of direct access volumes that can be mounted
concurrently as SPOOL volumes. The value must be a positive integer.
&NUMDA=2
- Specifying &NUMDA greater than the default may require increasing the
value of &BUFSIZE.
- During HASP initialization, if more than &NUMDA direct access volumes
whose volume serials begin with the characters SPOOL (see HASPGEN parameter
&SPOOL) are mounted, the message
MAXIMUM NUMBER OF &NUMDA SPOOL VOLUME(S) EXCEEDED
will be displayed on the console, and HASP will quiesce.
- See also HASPGEN parameter &NUMTGV.
- Mixtures of different supported SPOOL device types are permitted.
&NUMDDT
Specifies the number of Data Definition Tables (DDTs) to be assembled into
HASP. The specification should be an integer between 3 and 256, and equal to:
where
A = number of pseudo 1403 printers defined at SYSGEN
B = number of pseudo 2540 punches defined at SYSGEN
R =
&MAXXEQS * (maximum number of DD * or DD DATA cards per job)
&NUMDDT=10
- The pseudounit for &WTR should not be counted
in A above.
- If too few DDTs are specified, a permanent lockout condition can occur.
&NUMINRS
Specifies the number 2520 pseudo-punches to be used by the generated HASP
system as internal readers.
&NUMINRS=0
- If &NUMINRS is specified as or defaulted to zero, code to support the HASP
internal reader feature will not be included in the generated system.
- If more than &NUMINRS 2520 pseudo-punches have been defined during SYSGEN,
only the first &NUMINRS 2520 pseudo-punches can be used. It is permissible
to specify &NUMINRS greater than the number of 2520 pseudo-punches specified
at SYSGEN.
- The count of 2520 pseudo-punches is not included in HASPGEN parameter
&NUMDDT.
&NUMJOES
Specifies the number of Job Output Elements to be generated for queuing of
output work to printers and punches.
- &NUMJOES strongly influences the size of the third HASP checkpoint record,
which is calculated as:
If any checkpoint record is longer than the track size of the device on which
the primary SPOOL volume is mounted, HASP will not operate correctly.
- One Job Output Element is required for:
- Each unique class of SYSOUT that appears in a job queued for output.
- Each active printer or punch.
- Each interrupted or restarted job that is not currently active on a printer
or punch.
- Each unique combination of forms ID, UCS ID, FCB ID, FLASH ID (only
if &NUM3800 > 0) for all jobs currently
queued for output.
- Each job that was interrupted by a system failure (while printing or
punching) and has not yet been warm started on an output device.
- Too small a value results in jobs waiting for in-storage queuing for
completion of active print or punch work.
&NUMLNES
Specifies the largest teleprocessing line identification number (mm in
LINEmm) and the number of line definitions to be
generated in the HASP system. The value must be an integer between 0
and 99, inclusive. The value of &NUMLNES automatically becomes the
value of
&NUMRJE, unless
&NUMRJE is specified explicitly.
&NUMLNES=0
&NUMOACE
Specifies the number of overlay areas to be provided for the HASP Overlay
feature. The value must be an integer greater than zero.
&NUMOACE=2
- More than two overlay areas will benefit only a system with high
performance orientation (a very fast CPU or a workload consisting of a
large number of short jobs).
- See also parameter &OLAYLEV.
&NUMOSC
Specifies the number of OS consoles that HASP will support for
redirection of HASP command responses. The value must be an integer
between 1 and 32, inclusive, and should reflect the number of OS
consoles defined at system generation.
&NUMOSC=3
&NUMPRTS
Specifies the maximum number of physical printers HASP may use to print
job output. HASP supports 1403, 3211 and 3800 printers (if also supported
by the host operating system). The value must be a positive integer less
than or equal to 99.
&NUMPRTS=2
- If HASP initialization finds more printers defined to OS than the
value of &NUMPRTS, the message:
MAXIMUM OF &NUMPRTS PRINTER(S) EXCEEDED
is written to the console, and only the &NUMPRTS printers with the lowest unit
addresses are used by HASP.
- Although HASP will logically connect to supported printers (up to
&NUMPRTS) during initialization, those printers that are offline (as
indicated by a TIO) will not be used until they are physically switched
online and started by the operator.
- The value of &NUMPRTS influences the size of the HASP checkpoint record.
See Note 2 under &MAXJOBS.
- &BUFSIZE must be 536 or greater if HASP is to
use 3211 printers.
&NUMPUNS
Specifies the maximum number of physical punches HASP may use to punch
job output. HASP supports 3525, 2540 and 2520 card punch devices. The
value must be a positive integer less than or equal to 99.
&NUMPUNS=1
- If HASP initialization finds more punches defined to OS than the
value of &NUMPUNS, the message:
MAXIMUM OF &NUMPUNS PUNCH(S) EXCEEDED
is written to the console, and only the &NUMPUNS punches with the lowest unit
addresses are used by HASP.
- Although HASP will logically connect to supported punches (up to
&NUMPUNS) during initialization, those punches that are offline (as
indicated by a TIO) will not be used until they are physically switched
online and started by the operator.
- The value of &NUMPUNS influences the size of the HASP checkpoint
record. See Note 2 under &MAXJOBS.
&NUMRDRS
Specifies the maximum number of physical card readers HASP may use to read
OS job streams. HASP supports 3505, 2540 and 2501 card readers. The
value must be a positive integer less than or equal to 99.
&NUMRDRS=1
- If HASP initialization finds more readers defined to OS than the
value of &NUMRDRS, the message:
MAXIMUM OF &NUMRDRS READER(S) EXCEEDED
is written to the console, and only the &NUMRDRS readers with
the lowest unit addresses are used by HASP.
- Although HASP will logically connect to supported readers (up to
&NUMRDRS) during initialization, those readers that are offline (as
indicated by a TIO) will not be available until they are physically
switched online and started by the operator.
&NUMRJE
Specifies the largest remote terminal identification number (nn in
RMTnn) and thus the remote terminal definitions
to be used by the generated HASP system. The value must be a positive
integer less than or equal to 99.
&NUMRJE=0
&NUMSMFB
Specifies the number of HASP SMF buffers to be assembled into the generated
HASP system. The value must be an integer greater than or equal to zero.
&NUMSMFB=5
- If &NUMSMFB is less than 2, HASP will not produce SMF records, and will not
take the IEFUJV exit.
- See also &SMFRSIZ.
&NUMTGV
Variable symbol &NUMTGV specifies the number of units (track groups)
into which each SPOOL volume will be divided for HASP allocation purposes.
The specification must be a positive integer no greater than the number of
tracks on the SPOOL device with the fewest tracks.
&NUMTGV=400
- The users should decide upon the number of tracks he requires in a
track group and then divide by that number the total number of tracks
(except alternate tracks) on a typical SPOOL device type at the
installation. For example, to obtain a track group size of ten tracks
on a 2314, the division would specify &NUMTGV=400. If the same
installation occasionally used a 3330 as a SPOOL device, the track
group size for the 3330 would automatically become 19 tracks.
- Specifying a large &NUMTGV may require increasing the value
of &BUFSIZE.
- For each SPOOL volume it finds, HASP initialization calculates
number of tracks per group by dividing the total number of tracks on
the volume by &NUMTGV. It then marks as unavailable all track
groups that lie partially or wholly outside the first extent of data
set SYS1.HASPACE on that volume.
&NUMTPBF
Specifies the number of HASP teleprocessing buffers (for HASP RJE) to be
assembled into the generated HASP system. The value must be an integer
greater than or equal to zero.
&NUMTPPR
Specifies the maximum number of HASP remote terminal (including MULTI-LEAVING)
printed output streams that can be active simultaneously. The value must be an
integer greater than or equal to zero.
- If any remote terminal is to receive printed output, &NUMTPPR must
not be zero.
- &NUMTPPR influences the size of the HASP checkpoint record; see Note 2
for &MAXJOBS.
&NUMTPPU
Specifies the maximum number of HASP remote terminal (including MULTI-LEAVING)
punched output streams that can be active simultaneously. The value must be an
integer greater than or equal to zero.
- If any remote terminal is to receive punched output, &NUMTPPU must
not be zero.
- &NUMTPPU influences the size of the HASP checkpoint record; see Note 2
for &MAXJOBS.
&NUMTPRD
Specifies the maximum number of HASP remote terminal (including MULTI-LEAVING)
input streams that can be active simultaneously. The value must be an
integer greater than or equal to zero.
If any remote terminal is to read cards, &NUMTPRD must not be zero.
&NUMWTOQ
Specifies the number of HASP Console Message Buffers (CMBs). The value must
be an integer greater than 2.
&NUMWTOQ=15
- If Remote Job Entry is used, more message buffers are needed. This
is especially true with console support for MULTI-LEAVING terminals.
- Serious system degradation can be caused by specifying too few
message buffers.
- During periods of high console activity, when no message buffers
are available, some noncritical HASP messages will be discarded to avoid
delaying the associated process. These noncritical messages include certain
RJE oriented messages (such as communication line error messages), execution
time/line/card excession messages (continued excession will be noted when
a message buffer becomes available), and certain I/O error devices on
HASP-controlled devices.
- The number of buffers specified should be sufficient to accommodate
all outstanding operator requests and still allow message processing to
continue (for example, each active local or remote output device that
is waiting for forms, UCS, or carriage setup will have an outstanding
request).
&OLAYLEV
Specifies a HASP overlay level to be used for assembly of the various
HASP control sections. Any potential overlay code defined (by the
$OVERLAY macro) with a residence factor greater than &OLAYLEV will be
assembled as resident code rather than overlay code.
&OLAYLEV must be an integer between 0 and 15, inclusive.
&OLAYLEV=15
- HASP uses only residence factors 4, 8, 12, and (for HASP initialization
only) 0.
- If &OLAYLEV=15, all potential overlay code will be assembled as
overlay code.
- If &OLAYLEV=0, all potential overlay code, except that in HASP
initialization, will be assembled as resident code. HASP main storage
requirements will be increased by approximately 24K over the HASP load
module produced with &OLAYLEV=15.
&OREPSIZ
Specifies the size in bytes of a table used to hold REP data for true
overlay code. The REPs associated with a particular section of true
overlay code will be applied to that code every time it is brought into
main storage from the HASP overlay library. &OLAYLEV must be either
0, or an integer not less than 10.
&OREPSIZ=50
- Each entry in the HASP Overlay REP Table consists of 8+n bytes
(2 <= n <= 256), where n is the number of contiguous bytes to be
changed in a section of overlay code.
- The table is used only if the operator specifies at HASP initialization
that REPs are to be used and if some of the REPs are for true overlay code.
- If the HASP Overlay REP Table is too small to handle all true
overlay REPs, HASP initialization displays the following message on
the console:
and HASP quiesces.
&OSC(n)
Subscripted variable symbols &OSC(n) specify OS job classes. A job selected
by HASP logical partition n will be submitted to OS with the job class
&OSC(n). Each specified value must be a single letter from A to O,
inclusive.
&OSC(1)=A |
&OSC(2)=B |
&OSC(3)=C |
&OSC(4)=D |
&OSC(5)=E |
&OSC(6)=F |
&OSC(7)=G |
&OSC(8)=H |
&OSC(9)=I |
&OSC(10)=J |
&OSC(11)=K |
&OSC(12)=L |
&OSC(13)=M |
&OSC(14)=N |
&OSC(15)=O |
- Only the first &MAXPART specifications,
&OSC(1) through &OSC(&MAXPART), will be used.
- HASP initialization issues &MAXPART OS
START commands for OS initiators as follows:
S INIT.HOSINIT&OSC(1),,,&OSC(1)
.
.
.
S INIT.HOSINIT&OSC(
&MAXPART),,,&OSC(
&MAXPART)
&OSINOPT
Specifies inclusion (YES) or exclusion (NO) of the HASP OS Input SPOOLing
option. If &OSINOPYES and a DD * or DD DATA statement specifies the DCB
keyword, HASP will pass the DD statement and the data following it to
the OS Reader/Interpreter; OS will perform input SPOOLing. If &OSINOPT=NO,
or if &OSINOPT=YES and no DCB parameter is specified on the DD * or DD DATA
statement, HASP will spool the input data.
&OSINOPT=NO
- Use of the &OSINOPT feature may require changes to the HOSRDR procedure,
specifically to region size, PARM field and IEFDATA DD statement.
- The &OSINOPT feature allows an input data set to be defined as a
direct access data set rather than as a pseudo unit record device. This
may permit more flexible use of the data set, in concatenations, for
example, and with the checkpoint/restart facility.
&OUTPOPT
Specifies the action to be taken when a job exceeds its estimated print
lines or punched cards. The value must be 0, 1 or 2. For &OUTPOPT=2,
output excession causes the job to be cancelled with a dump. For
&OUTPOPT=1, output excession causes the job to be cancelled without
a dump. For &OUTPOPT=0, output excession does not cause the job to
be cancelled.
&OUTPOPT=0
- Regardless of the setting of &OUTPOPT, output excession results in a
message being written to the console.
- If &OUTPOPT=2, a SYSUDUMP or SYSABEND DD statement should be provided
by the user if a storage dump is desired on output excession.
- For &OUTPOPT=1 or 2, the job will not be cancelled if the job step
task is terminating normally or abnormally at the time of output excession.
$OUTEX
Specifies the interval, in print lines or punched cards, whichever is
appropriate, at which messages will output limit excession messages will
be written to the console. The value must be an integer greater than zero.
&OUTPOPT=0 XXX fix
- Regardless of the setting of &OUTPOPT, output excession results in a
message being written to the console.
- If &OUTPOPT=2, a SYSUDUMP or SYSABEND DD statement should be provided
by the user if a storage dump is desired on output excession.
- For &OUTPOPT=1 or 2, the job will not be cancelled if the job step
task is terminating normally or abnormally at the time of output excession.
&PID(n)
Subscripted variable symbols &PID(n) specify the identifiers to be used
with for each HASP logical partition. Each value must be a unique
1- or 2-character string.
&PID(1)=1 |
&PID(2)=2 |
&PID(3)=3 |
&PID(4)=4 |
&PID(5)=5 |
&PID(6)=6 |
&PID(7)=7 |
&PID(8)=8 |
&PID(9)=9 |
&PID(10)=10 |
&PID(11)=11 |
&PID(12)=12 |
&PID(13)=13 |
&PID(14)=14 |
&PID(15)=15 |
- Only the first &MAXPART specifications,
&PID(1) through &PID(&MAXPART),
will be used.
- The identifiers &PID(n) are used in messages to and commands from the
operator. For example, when an operator issues the command "$TImm,list",
he is referring not to logical partition mm but to logical partition n,
where &PID(n)=mm.
&PRI(n)
Subscripted variable symbols &PRI(n) specify OS job priorities. A job
selected by HASP logical partition n will be submitted to OS with the
job priority &PRI(n). Each value must be an integer between 0 and 13,
inclusive.
&PRI(1)=7 |
&PRI(2)=7 |
&PRI(3)=7 |
&PRI(4)=7 |
&PRI(5)=7 |
&PRI(6)=7 |
&PRI(7)=7 |
&PRI(8)=7 |
&PRI(9)=7 |
&PRI(10)=7 |
&PRI(11)=7 |
&PRI(12)=7 |
&PRI(13)=7 |
&PRI(14)=7 |
&PRI(15)=7 |
- The priorities defined by &PRI(n) affect only OS execution.
The priority of a job in the HASP job queue is determined by parameters
&RPRT(m), &RPRI(m),
&XLIN(m), and &XPRI(m).
- Only the first &MAXPART specifications,
&PRI(1) through &PRI(&MAXPART),
will be used.
$PRIDCT
Specifies the number of print lines to appear on each HASP separator page
for output printed on local printers. The value must be an integer greater
than or equal to zero. If zero is specified, no separator page will be
printed on local printers.
$PRIDCT=61
- The equivalent HASPGEN parameter for remote terminal printers is
$TPIDCT.
- If the value is 30 or larger, the first 29 lines will be used to produce
job name, job number and SYSOUT class in block letters.
&PRIHIGH
Specifies a HASP priority to be associated with the HASP Priority
Aging feature. A job will not be priority-aged if its HASP priority is
or becomes greater than or equal to &PRIHIGH. The value must be an
integer between 0 and 15, inclusive.
&PRIHIGH=0
&PRILOW
Specifies a HASP priority to be associated with the HASP Priority
Aging feature. A job will not b priority-aged unless its HASP priority
is initially at least &PRILOW. The value must be an integer between
0 and 15, inclusive.
&PRILOW=5
&PRIRATE
Specifies the amount by which a job's HASP priority will be
incremented in 24 hours by the HASP Priority Aging feature.
For example, if &PRIRATE=3, a job's priority will be
incremented by one for every eight hours it remains in the system.
But a job's priority will not be incremented unless it is at least
&PRILOW, and will not be incremented above
&PRIHIGH. The value must be an integer
greater than or equal to zero. If &PRIRATE is specified
as zero, Priority Aging is excluded from the generated HASP
system.
&PRIRATE=0
- If &PRIRATE=0, parameters &PRILOW
and &PRIHIGH are not used.
- See also &RPRT(n), &RPRI(n),
&XLIN(n) and &XPRI(n).
- If a job's priority is specified on the /*PRIORITY control card,
the job will be priority aged if its priority is eligible.
&PRTBOPT
Specifies the printer buffering option to be used for local HASP
printers. The value must be either 1 (for single buffering) or 2
(for double buffering).
&PRTBOPT=2
&PRTFCB
Specifies the 1- to 4- character name of the forms control buffer
image or carriage tape that HASP initially assumes is mounted on
every local printer.
&PRTFCB=6
&PRTRANS
Specifies the translation option for lines of print not directed
to 3211 printers. The value must be YES (translate to upper case)
or NO (do not translate).
&PRTRANS=YES
- If &PRTRANS is YES, each line to be printed by a local 1403 or
any remote printer is first translated. Translation changes lower
case letters to upper case letters, and characters that are not
valid on a PN train to blanks.
- If any print train is to be used on a HASP-controlled local
1403 or remote printer that has characters not equivalent to those
on a PN train, &PRTRANS must be specified as NO.
- If all printers are 3211s (no 1403s or remotes), &PRTRANS
should be specified as NO.
&PRTUCS
Specifies the name of the print chain or print train that HASP
initially assumes is mounted on every local 1403 printer generated
with the UCS feature and on every local 3211 printer. The UCS
identifier can be modified by the operator individually by printer
using operator commands. The value should be one of: AN, HN, PN,
QN, RN, UN, A11, H11, P11, U11, or 0.
&PRTUCS=0
- A value of 0 causes HASP to bypass the UCS loading procedure on
all local printers until the UCS type of each printer is specified
by the operator.
- If a UCS value that is not valid for the type of printer being
accessed is encountered, HASP will issue a warning message and bypass
the UCS loading procedure.
- The UN and U11 values are provided for installation use to support
other types of print chains.
&PUNBOPT
Specifies the punch buffering option to be used for local HASP punches.
The value must be either 1 (for single buffering) or 2 (for double
buffering).
&PUNBOPT=1
&RDR
Specifies the unit address of a pseudo 2540 reader to be used by
HOSRDR to supply jobs to OS. The value must be a valid unit address,
specified during OS system generation as a pseudo 2540 reader.
&RDR=0FC
The unit address assigned to this parameter must not be included in the
R esoteric group name describing other pseudo 2540 readers.
$REPRDR
Specifies the unit address of a physical 3505, 2540 or 2501 card
reader from which HASP initialization will read REP cards, if
requested by the operator. The value must be a valid unit address.
$REPRDR=00C
$REPWTR
Specifies the unit address of a physical 1403 or 3211 on which each
REP card read is to be printed, if printing of REP cards is requested
by the operator. The value must be a valid unit address.
$REPWTR=00E
&RESCORE
Specifies an amount of storage in 1K bytes. HASP will always issue
a GETMAIN for additional storage; all additional storage except for
&RESCORE * 1K bytes will be used for HASP buffers.
&RESCORE=0
&RJOBOPT
Specifies the type of scan that should be performed on JOB cards
processed by the HASP input processor, and specifies whether an
illegal JOB card should prevent execution of the associated job.
The specification must be an integer between 0 and 5, inclusive,
where the specified values have the following meanings:
Value |
Scan HASP Parameters |
Terminate on HASP Parameter Error |
Terminate on OS Format Error |
0 | YES | YES | YES |
1 | YES | YES | NO |
2 | YES | NO | YES |
3 | YES | NO | NO |
4 | NO | -- | YES |
5 | NO | -- | NO |
&RJOBOPT=2
- JOB card parameters CLASS, MSGCLASS and TYPRUN=HOLD are always
scanned.
- The HASP JOB card parameters scanned are those in the JOB card
accounting field: (pano,room,time,lines,cards,forms,copies,log,linect).
- An OS format error is any error that prevents HASP from continuing
its scan of the JOB statement. OS format errors are defined in the
OS Job Control Language Reference, and include such things as illegal
continuation, illegal characters, and missing parenthesis.
RMTnn
Ordinary symbols RMTnn specify the characteristics
of remote terminals to be used with HASP Remote Job Entry.
Terminals must be defined consecutively, starting with RMT01.
Each specification must be a 14-character string of the form:
RMTnn=mmooppiillwtdf
where the letters represent the following:
Code Letters | Range | Description |
nn | 01-99 | Remote number |
mm | 01-99 | Line number (** indicates /*SIGNON assignment) |
oo | 00-99 | Print routing (remote number) |
pp | 00-99 | Punch routing (remote number) |
ii | 00-15 | Priority increment for this remote |
ll | 00-15 | Priority limit for this remote |
w | 0-6 | Printer width as follows: |
| | 0 = 80 characters |
| | 1 = 100 characters |
| | 2 = 120 characters |
| | 3 = 132 characters |
| | 4 = 144 characters |
| | 5 = 150 characters |
| | 6 = 96 characters |
t | 0-7 | Terminal type as follows: |
| | 0 = 2770 |
| | 1 = 2780 |
| | 2 = 2922, System 360/20 Submodel 2, 4, 6 |
| | 3 = System 360/20 Submodel 5 |
| | 4 = System 360/22, 25, 30, 40, etc. |
| | 5 = 1130 |
| | 6 = System/3 |
| | 7 = 3780 |
d | 0-4 | Data Format as follows: |
| | 0 = Unblocked fixed length |
| | 1 = Blocked fixed length |
| | 2 = Unblocked variable length (Note - use this
for basic 2770 terminals.) |
| | 3 = Blocked variable length (Note - use this
for all 3780 and 2780 terminals and for
2770 terminals with Buffer Expansion.) |
| | 4 = Programmable interface (Note - use this
for all BSC MULTI-LEAVING interfaces.) |
f | | Terminal features as follows: |
| 0-9 | 3780 Terminal features |
| |
f | Compress Expand | Horizontal Format Control | Transparency |
0 | No | No | No |
1 | No | No | Yes |
4 | No | Yes | No |
5 | No | Yes | Yes |
8 | Yes | No | No |
9 | Yes | No | Yes |
|
| 0-@ | 2770 Terminal features |
| |
f | Compress Expand | Horizontal Format Control | Additional Buffer Expansion | Transparency |
0 | No | No | No | No |
1 | No | No | No | Yes |
2 | No | No | Yes | No |
3 | No | No | Yes | Yes |
4 | No | Yes | No | No |
5 | No | Yes | No | Yes |
6 | No | Yes | Yes | No |
7 | No | Yes | Yes | Yes |
8 | Yes | No | No | No |
9 | Yes | No | No | Yes |
# | Yes | No | Yes | No |
@ | Yes | No | Yes | Yes |
|
| 0-7 | 2780 Terminal features |
| |
f | Compress Expand | Horizontal Format Control | Transparency |
0 | No | No | No |
1 | No | No | Yes |
2 | No | Yes | No |
3 | No | Yes | Yes |
4 | Yes | No | No |
5 | Yes | No | Yes |
6 | Yes | Yes | No |
7 | Yes | Yes | Yes |
|
| 0-3 | MULTI-LEAVING Terminal features |
| |
f | Console Support | Transparency |
0 | No | No |
1 | No | Yes |
2 | Yes | No |
3 | Yes | Yes |
|
RMTnn=**nn0000153131
- Parameter &NUMRJE must specify the number of specifications
(RMTnn) to be included in the generated HASP system.
- No two specifications (RMTnn) may specify the same line
number (mm). If ** is specified instead of a line number for
mm, the associated remote terminal may connect to HASP via
any suitable line. HASP will logically connect the terminal
with the line when it recognizes the /*SIGNON control card.
If line number is specified explicitly, the associated
terminal need not use a /*SIGNON card.
- The line number specification mm refers to line specification
LINEmm, which in turn specifies the unit address of the line.
- For print and punch routing, a specification of 00 causes
output from jobs submitted at the remote terminal to be
printed/punched locally, unless rerouted.
- Priority increment is the value to be added to the priority
of a job submitted from the remote terminal.
- Priority limit is the maximum value of priority for any job
submitted from the remote terminal.
- For a basic 2770 (128-byte buffers), printer width must be
specified as 120 characters or less.
- Printed and nontransparent punched output to a basic 2770
will be variable-blocked up to the limit of the 128-byte
buffers, even though the data format must be specified as
variable-unblocked.
- The following table gives, for &TPBFSIZ,
minimum values required to support various nonprogrammable
terminals:
Minimum &TPBFSIZ | Terminal Type, Features |
128 | 2770 basic |
260 | 2770 with Buffer Expansion |
400 | 2780 |
516 | 2770 with Buffer Expansion and Additional Buffer Expansion |
516 | 3780 |
See also parameters &TPBFSIZ and
&MLBFSIZ.
- The 3780 plus the 3781 punch must be generated as a 2770 with
appropriate features in order to get output device component
selection. For example, the last three characters of the RMTnn
parameter would be 739 for a 3780 alone with transparency and
03@ for a 3780 plus 3781 punch with transparency.
$RPRBOPT
Specifies the printer buffering option to be used for all printers at
HASP remote terminals. The value must be either 1 (for single
buffering) or 2 (for double buffering).
$RPRBOPT=1
The specified value refers to HASP regular buffers, not to HASP
teleprocessing buffers.
&RPRI(n)
Subscripted variable symbols &RPRI(n) specify job priorities
corresponding to intervals defined by subscripted variable symbols
&RPRT(n). If a user does not supply a
/*PRIORITY control card with his job, the queueing priority is
completed as described in Note 1 below. Each &RPRI(n)
specification must be an integer between 0 and 15, inclusive.
&RPRI(1)=9 |
&RPRI(2)=8 |
&RPRI(3)=7 |
&RPRI(4)=6 |
&RPRI(5)=5 |
&RPRI(6)=4 |
&RPRI(7)=3 |
&RPRI(8)=2 |
&RPRI(9)=1 |
- The queueing priority is computed as:
The subscript n is the smallest number for which:
The subscript m is the smallest number for which:
where t is the estimated execution time from the accounting field of
the JOB card or from the /*JOBPARM control card, and o is the sum of
the estimated output lines and cards from the accounting field of the
JOB card or from the /*JOBPARM control card.
- See the description of &RPRT(n).
- See also the description of &XPRI(m)
&RPRT(n)
Subscripted variable symbols &RPRT(n) specify estimated execution times
which are associated with the priorities
&RPRI(n).
Each value must be an integer between 1 and X'FFFFFF'/60, inclusive.
&RPRT(1)=2 |
&RPRT(2)=5 |
&RPRT(3)=15 |
&RPRT(4)=X'FFFFFF'/60 |
&RPRT(5)=X'FFFFFF'/60 |
&RPRT(6)=X'FFFFFF'/60 |
&RPRT(7)=X'FFFFFF'/60 |
&RPRT(8)=X'FFFFFF'/60 |
&RPRT(9)=X'FFFFFF'/60 |
- See the description of &RPRI(n).
- See also the description of &XPRI(m)
- These values are not used if the job contains a /*PRIORITY HASP
control card.
&RPS
Specifies inclusion (YES) or exclusion (NO) of Rotational Position
Sensing (RPS) code for all HASP channel programs directed to direct
access devices with the RPS feature.
&RPS=NO
Regardless of the setting of &RPS, HASP will correctly operate with
and supported direct access device or combination of devices.
$RPUBOPT
Specifies the punch buffering option to be used for all punches at
HASP remote terminals. The value must be either 1 (for single
buffering) or 2 (for double buffering).
$RPUBOPT=1
&SMFRSIZ
Specifies the size in bytes of the largest SMF record to be written
by HASP, or the size of one SMF common exit parameter area, whichever
is greater. If SMF records are to be written by HASP, the value must
be an integer equal to or greater than 228.
&SMFRSIZ=228
- If &NUMSMFB is less than 2, &SMFRSIZ
will be ignored. Otherwise, HASP will generate SMF records and
&SMFRSIZ will be the maximum size SMF record written by HASP.
- See also parameter &NUMSMFB.
&SPOLMSG
Specifies the number of physical spool records in the first extent
of SYS1.HASPACE on the primary SPOOL volume to be reserved for
operator messages and HASP messages for HASP remote terminals.
Each physical record is capable of holding one or more messages
for a single remove terminal. Messages are held if they are
directed to:
- Any terminal not signed on.
- Any signed-on hardware terminal that is currently processing
an input or output stream.
- Any signed-on computer terminal that is not a MULTI-LEAVING
terminal with a console.
If a message is to be held but no space is available to hold it,
the message is discarded without operator notification.
The value for &SPOLMSG must be an integer greater than or
equal to zero. If &SPOLMSG is zero, no messages will be sent
to hardware terminals.
- Only the $DM command can generate messages to a remote terminal
that is not signed on.
- For signed-on terminals, messages are generated for job-on-reader,
by $DM, and as responses to commands from the terminal.
- Each message to a terminal (except to a MULTI-LEAVING remote
defined with a console) is held until it can be printed, or until
HASP is restarted.
&SPOOL
Specifies the first five characters of the volume serial of each
direct access volume mounted for HASP use as a SPOOL volume.
The value must be exactly five characters and must be valid as
a volume serial.
&SPOOL=SPOOL
HASP requires that at least the primary spool volume (normally SPOOL1)
be mounted. For example, if &SPOOL=$-#-@, HASP would require at least
$-#-@1 be mounted.
&TIMEOPT
Specifies the action to be taken when a job's estimated execution time
is exceeded. The value must be one of the integers 0, 1, 2 or 4. For
&TIMEOPT=4, the job's time limits will not be monitored. For
&TIMEOPT=2, time excession causes the job to be cancelled with a
dump. For &TIMEOPT=1, time excession causes the job to be cancelled
without a dump. For &TIMEOPT=2, &TIMEOPT=1 or &TIMEOPT=0,
time excession causes messages to be written to the console.
&TIMEOPT=4
- See also $ESTIME, which applies for
&TIMEOPT=0, &TIMEOPT=1 and &TIMEOPT=2.
- For &TIMEOPT=1 or &TIMEOPT=2, the job will not be cancelled
if the job step task is normally or abnormally terminating when time is
exceeded.
$TIMEXS
Specifies the interval, in minutes, at which messages will be written
to the console indicating that a job's estimated execution time is
exceeded. The value must be an integer greater than zero.
$TIMEXS=1
- The first time excession message is written when the job's
and estimated execution time has been exceeded.
- If the &TIMEOPT value is
greater than 2, $TIMEXS is not used.
&TPBFSIZ
Specifies the size in bytes of each HASP teleprocessing buffer. The
value must be a positive integer less than or equal to 32K.
&TPBFSIZ=400
- The value of &TPBFSIZ is the maximum size of any HASP
teleprocessing buffer. See also &MLBFSIZ,
which must be less than or equal to &TPBFSIZ.
- HASP remote terminal programs are MULTI-LEAVING programs and
using &MLBFSIZ.
$TPIDCT
Specifies the number of print lines to appear on each HASP job
separator page for printed output directed to any HASP remote
terminal. The value must be an integer greater than or equal
to zero. If the value is zero, no separator page will be produced
on remote printers.
$TPIDCT=6
- The equivalent HASPGEN parameter for local printers is
$PRIDCT.
- If the value is 30 or greater, the first 29 lines will be used to
produce job name, job number and SYSOUT class in block letters.
&TRACE
Specifies inclusion or exclusion of the HASP event tracing facility in
the generated HASP system. The value defines the number of entries
to be generated in the HASP trace table. If &TRACE is zero, even
tracing is excluded. The value must be an integer greater than or
equal to zero.
&TRACE=0
- The HASP trace facility is a development tool that causes system
degradation, and causes the OS SPIE mechanism to work incorrectly.
HASP trace should not be included in any generated HASP system
intended for normal production.
- The &TRACE option is independent of the
&DEBUG option.
&TSOSTCN
Specifies inclusion (YES) or exclusion (NO) of support for TSO STATUS
and CANCEL commands for jobs submitted by TSO users through the HASP
internal reader.
&TSOSTCN=NO
If &TSOSTCN is set to NO, any attempt to find a HASP-controlled
job using a STATUS or CANCEL command will receive a JOB NOT FOUND
response.
&USASCII
Specifies inclusion (YES) or exclusion (NO) in the HASP Remote Terminal
Access Method of the capability to use USASCII line-control characters
as well as EBCDIC line-control characters.
&USASCII=NO
$WAITIME
Specifies a time interval in seconds. For hardware terminals, the
HASP Remote Terminal Access Method will wait $WAITIME seconds at the
completion of processing of any input stream, printed output stream,
or punched output stream, to allow the operator to alter the normal
sequence of Remote Job Entry operations. The value must be an integer
greater than zero.
$WAITIME=1
&WCLSREQ
Specifies optional requeuing for OS output classes specified by
&WTRCLAS.
The HASP writer subtask (load module HASPWTR) processes System
Message Blocks (SMBs) for jobs queued in the OS output queues defined
by &WTRCLAS. After processing a job whose
output class is the nth character of &WTRCLAS,
HASPWTR examines the nth character of &WCLSREQ. If the nth
character of &WCLSREQ is *, HASPWTR deletes the job from the OS job
queue. But if the nth character of &WCLSREQ is an OS output
class, HASPWTR requeues the job in the OS output queue specified by
the nth character of &WCLSREQ (which must be different from any
class specified in &WTRCLAS).
The specification must be a string of one to eight characters, each
of which is either * or a unique, valid OS output class different from
any specified in &WTRCLAS. If more characters are
specified in &WCLSREQ than were specified in &WTRCLAS,
the excess characters in &WCLSREQ are unused.
&WCLSREQ=********
- The output requeuing option is useful for providing an extra copy
of a job's system messages to a TSO user's terminal.
- A requeued job is not subsequently available through HASP, but must
be accessed by a standard OS output writer or similar mechanism.
- A requeued job may contain a mixture of system messages and SYSOUT
data sets of the same class, if the SYSOUT data sets were SPOOLed by
OS (see HASPGEN parameter $$x). HASPWTR does not
process the SYSOUT data sets, but requeues the entire job containing
them in the new class specified by &WCLSREQ. The system messages
and SYSOUT data sets are then available to a standard OS output writer
that is processing the new class.
- Any DD statements in the system messages of a requeued job that
were originally coded as DD * or DD DATA and were SPOOLed by HASP
rather than OS (see HASPGEN parameter &OSINOPT) will appear to a
writer processing a &WCLSREQ class as DD $ and DD CATA, respectively,
and will print that way unless the writer is programmed to change
them back to their original form.
&WTR
Specifies the unit address of a pseudo 1403 printer to be used as a
writer to retrieve System Message Blocks (SMBs) from the OS job queue
for jobs controlled by HASP. The value must be a valid unit address,
specified during OS system generation as a pseudo 1403 printer.
&WTR=0FE
The unit address assigned to this parameter must not be included in
the A estoteric group name describing other pseudo 1403 printers.
&WTRCLAS
Specifies the OS system output classes to be processed by HASP.
The value must be one to eight unique characters, each of which
is a valid OS output class different from any specified in
&WCLSREQ.
&WTRCLAS=A
- HASP examines the MSGCLASS parameter of every JOB card it sends to
OS. If MSGCLASS is not specified or is not one of the classes specified
by &WTRCLAS, HASP adds a MSGCLASS parameter specifying the leftmost
character of &WTRCLAS.
- If a job submitted to OS by HASP has certain errors on the JOB card,
the OS reader/interpreter will fail the job and change its MSGCLASS to
a default class specified in the EXEC statement PARM field of the HOSRDR
procedure. This default class must be specified in &WTRCLAS, or HASP
will not work correctly.
- See also HASPGEN parameter $$x.
&XBATCHC
Specifies a list of the job classes to be used with the Execution
Batch Scheduling feature. The specified classes are excluded from
running jobs outside Execution Batch Scheduling. The value for &XBATCHC
must be a string of one to eight characters (letters and numbers) that
are valid unique HASP job classes. If &XBATCHC is left at its
default value, the generated HASP system will not include Execution
Batch Scheduling.
&XBATCHC=[null string]
If &XBATCHC is not specified, then
&XBATCHN
is not used.
&XBATCHN
Specifies the first five characters of the name of each OS job to be
started internally by HASP when required for the execution of a user
job under the Execution Batch Scheduling feature. The value must be
a five-character string, with the first character alphabetic or
national and the remaining four characters alphameric or national.
&XBATCHN=$$$$$
If
&XBATCHC is specified, HASP will reject
all user submitted jobs whose job names start with the five characters
in &XBATCHN.
&XLIN(m)
Subscripted variable symbols &XLIN(m) specify output record counts
which are associated with the priorities
&XPRI(n).
Each value must be an integer between 1 and 16,777,215.
&XLIN(1)=2000 |
&XLIN(2)=5000 |
&XLIN(3)=15000 |
&XLIN(4)=X'FFFFFF'/60 |
&XLIN(5)=X'FFFFFF'/60 |
&XLIN(6)=X'FFFFFF'/60 |
&XLIN(7)=X'FFFFFF'/60 |
&XLIN(8)=X'FFFFFF'/60 |
&XLIN(9)=X'FFFFFF'/60 |
- See the description of &XPRI(n).
- See also the description of &RPRI(m)
- These values are not used if the job contains a /*PRIORITY HASP
control card.
&XPRI(m)
Subscripted variable symbols &XPRI(m) specify output priorities
that correspond to intervals defined by subscripted variable symbols
&XLIN(m). If a user does not supply a
/*PRIORITY control card with his job, the job's priority is
recomputed after execution, based on the actual number
of print and punch records it produced. If the job produced
p print lines and
c punched cards, its output
priority will become &XPRI(m), where m is the smallest
number for which:
Each value must be an integer between 0 and 15.
&XPRI(1)=9 |
&XPRI(2)=8 |
&XPRI(3)=7 |
&XPRI(4)=6 |
&XPRI(5)=5 |
&XPRI(6)=4 |
&XPRI(7)=3 |
&XPRI(8)=2 |
&XPRI(9)=1 |
$$x
Specifies the destination for an output data set designated in the user's
JCL as SYSOUT=x. The value must be one of the characters A, B or *.
These characters indicate:
- $$x=A SYSOUT data sets for class x will normally be printed.
- $$x=B SYSOUT data sets for class x will normally be punched.
- $$x=* SYSOUT data sets for class x be processed entirely by OS.
In this case, HASP will add "UNIT=SYSDA" to the SYSOUT DD statement
unless the user has already coded UNIT= information.
| $$A=A |
| $$S=A |
| $$B=B | | $$T=A |
| $$C=A | | $$U=A |
| $$D=A | | $$V=A |
| $$E=A | | $$W=A |
| $$F=A | | $$X=A |
| $$G=A | | $$Y=A |
| $$H=A | | $$Z=A |
| $$I=A | | $$0=A |
| $$J=A | | $$1=A |
| $$K=B | | $$2=A |
| $$L=A | | $$3=A |
| $$M=A | | $$4=A |
| $$N=A | | $$5=A |
| $$O=A | | $$6=A |
| $$P=A | | $$7=A |
| $$Q=A | | $$8=A |
| $$R=A | | $$9=A |
- If a job's JCL includes the second positional parameter in a
SYSOUT parameter (user writer name), the output will be processed
entirely by OS, regardless of whether the corresponding $$x parameter
was specified as *.
- If a give output class x is one of the classes assigned to &WTRCLAS,
it must not be used in a SYSOUT specification to be processed by OS
unless that class is subject to requeueing as described under the
description of parameter &WCLSREQ.
Home >
Hercules >
HASP V4 >
HASPGEN Parameters