Surrogate RJS for UCLA-CCN
J. R. Pickens · 1973
By using UCSB's Network Standard RJS* users can now gain access to UCLA-CCN's RJS without converting to the UCLA protocol.In addition, the need to use and create files in an intermediate host is avoided.For example, TIP users may operate with hot card readers and printers through UCSB's Remote Job Server and have their jobs execute at UCLA-CCN.The disadvantages of this scheme as compared to direct connections to UCLA are as follows:1.A small amount of additional JCL is required to route jobs from UCSB to UCLA.2. A UCSB batch account must be opened.3. Turnaround time includes waits in UCSB batch queues.4. The current implementation requires separate submission and retrieval steps.5. The RJS terminal used for submission/retrieval at UCLA-CCN should not be accessed online until all transfers to/from UCSB are complete.Hopefully, these disadvantages are outweighed by the convenient interface to standard RJS.Attached is the document which describes this procedure to access UCLA-CCN.