RSX11M V3.1 BATCH RSX11M will spawn a new copy of each MCR utility up to one copy per terminal. Unfortunately, this advantage can also become a problem in a system with limited total and dynamic memory. Problems usually only develop if a large number of copies of the larger tasks are spawned( ie everyone is compiling and taskbuilding F4P tasks). BATCH is used to circumvent this problem by forcing F4P compil- ations and taskbuilds to occur in a single stream, ie only a single compilation or taskbuild will occur at a single time. During most of the day, this will not adversly affect turnaround time, however, it will slow down work at peak load times. This disadvantage is offset by people being allowed to continue to use the system at times during which they otherwise might have to be requested to log off. Further HELP using BATCH can be found by typing HELP BATCH keyword, where keywords are ; BATCH How BATCH works ; @BATCH Generating a BATCH command file ; QUEUE Displaying one's position in the batch queue. ; SUBMIT SUBMIT command line ; CHANGES Changes to BATCH for V3.2 2 BATCH BATCH works using a virtual terminal VT0: Each SUBMIT command includes in it the user's logon UIC, PASSWORD, and command file. BATCH then logs the user onto VT0:. If the logon is successful the command file will be processed by a copy of PIN. All output to the virtual terminal will be out to a log file(with extension .LOG;1). For example the command SUBMIT GGG/MMM/PASWRD FOO Will try logging the user onto the account [GGG,MMM] with a password PASWRD. After logon, the file FOO.PRC will be processed by PIN. When the command file is finished by PIN, BATCH notifies the initiating terminal that the command file has finished execution. One can then use PIP to display the contents of the LOG file. PIP TI:=FOO.LOG or LIST FOO.LOG 2 @BATCH To aid the user in using the BATCH facility, an indirect command file, @BATCH exists. @BATCH will create a compilation and taskbuild file and SUBMIT them for batch processing the first time. If one wishes to compile and build a task MYTSK, @BATCH will create MYTSK.PRC. If at any time the user wishes to re- SUBMIT his source for compilation and taskbuilding, all he need type is SUBMIT GGG/MMM/PASWRD MYTSK where GGG and MMM are from his UIC=[GGG,MMM], and PASWRD is the user's LOGON PASWRD, and where MYTSK is the name for MYTSK.PRC. 2 SUBMIT SUBMIT is the command line dispatcher to BATCH. The syntax is SUB{mit} GGG/MMM/PASWRD COMMANDFILE where the 'mit' in braces is optional, and GGG and MMM are the user's group and member numbers respectively as found from UIC=[GGG,MMM]. PASWRD is the user's logon paswrd. COMMANDFILE is the name of the BATCH command file. The extension of the command file must be .PRC. However, the extension must not be typed in. If @BATCH has been used, the file TASKNAME.PRC already exists on the user's UIC may be used to build the user's task, TASKNAME. 2 QUEUE BTQ is a task (MCR) which displays those command files still in the BATCH queue. BTQ's display format depends on whether or not the user is privleged or non privleged. If the user is privleged, BTQ displayes the exact command the user SUBMITTED to BATCH, ie. GRP/MEM/PASSWORD CMDFILE If the user is non-privleged, only the queue of command files is displayed. If a user has submitted a job to BATCH, and it has not yet finished, either the command file will be listed by BTQ, or BATCH is processing the file and is not yet done. If BATCH needs to be aborted for any reason, or the system halted, a PRIOR use of BTQ will enable all command files(except the one in progress) to be restarted. 2 CHANGES For V3.2 several changes to BATCH have been made. The most noticible is that the command file name for submittal to batch has changed. The file extension type is now .PRC. This is because ...AT. no longer process the BATCH taskbuild and assembly procedure. The task PIN now serves that function. Please note, PIN can not process the old format command file. It will process only simple MCR commands. The old command files will not work. You may use @BATCH as before to create a BATCH command file. ALso BLD.CMD and OPT.CMD can be used to create general purpose command files suitable for processing via PIN.