Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!RELAY.CS.NET!macmillan%wnre.aecl.cdn%ubc.CSNET From: macmillan%wnre.aecl.cdn%ubc.CSNET@RELAY.CS.NET.UUCP Newsgroups: mod.computers.vax Subject: card reader input symbiont Message-ID: <657*macmillan@wnre.aecl.cdn> Date: Thu, 4-Dec-86 14:38:07 EST Article-I.D.: wnre.657*macmillan Posted: Thu Dec 4 14:38:07 1986 Date-Received: Sun, 7-Dec-86 04:53:59 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 65 Approved: info-vax@sri-kl.arpa We are running the HASP+ communications "package" between our VAX cluster and a remote CDC system. It allows users to submit jobs to be executed on the CDC and receive the output from the jobs on a VAX printer or to the user's directory. I am trying to come up with a simple mechanism that would allow CDC users to submit jobs to the VAX batch queues and automatically receive output on the CDC. The plan is: 1. CDC user prepares a VAX job for input to a card reader (ie. $job, $password, etc.) 2. The user routes the job to the remote (ie the VAX) punch queue. The job has an additional parameter containing the CDC userid and password which will be used to route the job back to the CDC. Somthing like /CDCID=(aaaaa,bbbbb). This information is then stripped off the $job card. 3. A /NOPRINT and /LOG_FILE=filename is appended to the $job card. The job is then submitted to the card reader input symbiont. $ MCR INPSMB filename $ 4. A follow up job, synchronized to run immediately after the first, routes the job to the CDC. Actually, it submits a file to the CDC, with the printout of the job from step 3, appended to it. The purpose of a follow-up job is to ensure that something gets back to the CDC. An alternative is to add on the DCL, but suppose the job failed for cputime, DCL error, or anything else? Something HAS to be returned, or the CDC user will have no record of what happened. $ SYNCHRONIZE/ENTRY=number/QUEUE=name The Problem: The only hitch in the plan is in the follow-up job. It needs to know the entry number of the job in the batch queue. (The queue name can be extracted from the $job card beforehand.) But INPSMB does not return the entry number (or anything else) to the terminal. Note: The followup job will have a different user name than the first job. Is there a simple solution? Maybe a simple $ ON ERROR GOTO ROUTEBACK . . . $ ROUTEBACK: !comes here if error or not $ SUBMIT FOLLOWUP I want to keep things as simple as possible, and write a program that calls on the input symbiont, only as a last resort. John MacMillan Atomic Energy of Canada Whiteshell Nuclear Research Establishment Pinawa, Manitoba, Canada R0E 1L0 (204) 753-2311 x2539