Managing Multiple SNA Gateways and the Routing of Remote Job Entry (RJE) Output to Multiple Destinations Fall 1989 DECUS Symposium NE037, November 9, 1989 Al Grosser Pat Scopelliti Corning Incorporated Corning, New York Agenda History of configuration IBM 3270/TE Access Control RJE Routeback RJE Checker Summary History of Configuration Problems and issues we encountered: - SNA Gateways scattered all over company - Most were under-utilized - Three more sites were about to buy a gateway - Remote sites were difficult to support - About 50 isolated DECnet networks - High communications cost for remote sites using both SNA and DECnet - Variety of SNA communications devices in use caused support issues: · IBM 5280 · HASPBOX · COMBOARD · DEC DECSA-based History of Configuration What we did: - Acquired one DECnet Router - Expanded a second Router - Moved twelve SNA Gateways to Corporate Data Center - Allocated five for TE/3270 - Allocated eight for dedicated LUs PrE, RJE, DTF, API - Converted leased circuits from SNA/SDLC to DECnet/DDCMP - Eliminated a number of IBM 5280 and HASP COMBOARDs History of Configuration What was still missing: - Load balancing on TE gateways - RJE output routing - RJE uptime What we added: - IBM 3270/TE Access Control - RJE Routeback System - RJE Checker IBM 3270/TE Access Control Objectives: - Share the load over multiple gateways - Maximize availability - Security - Usage charges IBM 3270/TE Access Control Implementation: · Client/Server Model Components: · Server portion, runs on multiple nodes SCANNER.EXE DB Manager SELECTOR.EXE · Client portion IBM.EXE · Other Database administration front-end (future) Billing software IBM 3270/TE Access Control System logic flow: +------+ +-----+ | DB | | DB | +------+ +-----+ | G/W | |Valid| |in Use| |Users| +-----+ +------+ +-----+ | G/W | | | +-----+\ | +-----+ | \ V | DB | V +-----+ \ +-------+ +-----+ +--------+ +-------+ | G/W |--->|SCANNER|--->|Avail|--->|SELECTOR|<--->|IBM.EXE|---> User +-----+ / +-------+ | G/W | +--------+ +-------+ | / +-----+ | | +-----+/ | | | G/W | V | +-----+ +-------+ | |SNATERM|<-----+ +-------+ G/W Gateway DB Database IBM 3270/TE Access Control SCANNER.EXE: - Scans active gateways on a regular basis - Uses definition file containing · Active gateways · Available access names · Allows us to test a new server or remove a server from use - Scans each active gateway for current loading · LUs in use / Active LUs - Updates availability database for SELECTOR Session Activity Report $ TYPE SNAGWY::"TASK=...SSL" LC-1 Act 1 Act/Ses 2 Act/Ses 3 Act/Ses 4 Act/Ses 5 Act/Ses 6 Act/Ses 7 Act/Ses 8 Act/Ses 9 Act/Ses 10 Act/Ses 11 Act/Ses 12 Act/Ses 13 Act/Ses 14 Act/Nose 15 Act/Nose 16 Act/Nose 17 Act/Ses 18 Act/Ses 19 Act/Ses 20 Act/Ses 21 Act/Ses 22 Act/Nose 23 Act/Nose 24 Act/Nose 25 Act/Ses 26 Act/Ses 27 Act/Ses 28 Act/Ses 29 Act/Ses 30 Act/Nose 31 Act/Nose 32 Act/Nose LC-2 Inact $ Yet another Digital undocumented feature ;-) This is used for the DECSA-based SNA Gateways. Microserver-based SNA gateways (ST and CT) use the supported image SNANCP. IBM 3270/TE Access Control SELECTOR: - Invoked through a DECnet object by IBM.EXE - Verifies user against user database - Determines least loaded Gateway offering requested access name - Returns: · Selected gateway or error condition · News message · Access controls for gateway - Logs events in an event log for billing and security purposes IBM 3270/TE Access Control IBM.EXE - Primary user interface to IBM host - Replaces SET HOST/SNA - Sends connect request to SELECTOR · nodename, username, access requested - Handles SELECTOR's response · Error handling · News message - Builds and executes SET HOST/SNA using · returned access information · access requested - Handles primary and secondary server systems which are normally on-line and available - Handles tertiary server system for disaster recovery IBM 3270/TE Access Control Database administration - Currently a manual process - Entry for each authorized nodename/username containing: · Security information · Accounting information - Future: Rdb/DTR interface Billing Software - Gathers and distributes billing records - Assimilates activity and incorporates data into corporate accounting system - Generates a summary report IBM 3270/TE Access Control Results: - High availability · Multiple gateways · Multiple servers - High performance · User gets least loaded gateway - Enhanced security · Only authorized users have access - Enhanced user tracking RJE Routeback SEND - Replacement for SUBMIT/SNA Adds support for user-specified output routing - Makes entry in routeback database - Output can go to any of: · Directory/file · VMS Print queue · Mail (high security) · VMS Batch job (RJE output file specification passed as parameter P1) - Adds notification of output arrival - Keys off ROOM, JOBNAME, FORMNAME of RJE output - Adds /TEMPORARY qualifier for one-shot routeback RJE Routeback SEND/ENTER - Makes entry in routeback database - Ad-hoc specification of output routing - No job submitted to IBM host SEND/REMOVE - Removes entry from routeback database SEND/RT - Lists entries in routeback database RJE Routeback Routeback is effected by assigning IBM JES2 streams to a network-only routeback account whose login command file receives the file and determines where the output is to be delivered. For example: SNARJE> ASSIGN VAXEN"RMT12_PR1":: PR1 /NOSPOOL Steps performed: - Runs FAL to receive the file from the SNA Gateway - Determines JOBNAME, ROOM, and FORMNAME - Scans routeback database for a match - If no match found, just print it (default action) - If match found, process file according to routeback entry's contents - If output was directed to a user directory/file, the file copy is done using the user's UIC for security reasons - Logs all events in a logfile DCL code fragment showing FAL execution $ workfile = "snarje_''f$getjpi("","PID")'.tmp" $! $! Capture FAL's activity (includes filename created) $! $ define fal$log 1 $ define fal$output 'workfile' $! $! Now run FAL to receive the file $! $ run sys$system:fal.exe $! $! Parse the logfile to determine the resultant file $! $ open/read f1 'workfile' $file_loop1: $ read/error=no_file f1 record $ reclen = f$length(record) $ if f$locate("Create file",record) .eq. reclen - then goto file_loop1 $file_loop2: $ read/error=no_file f1 record $ if f$locate("Resultant file: ",record) - .eq. reclen then - goto file_loop2 $ rcvd_file = f$extract(16,255,record) $ close f1 $! $! Symbol RCVD_FILE contains resultant filename RJE Checker Consists of two components: - Checker command file - User interface Checker - Runs interactively or as a batch job - Checks workstation status - If not active · Determines RJE server status · Determines RJE multiplexer status · Determines DECnet status · Determines gateway status · Restores RJE workstation to last known state · Logs a message · Sends mail to manager, reporting problem description RJE Checker User interface - Primary interface for users entering JES2 console commands - Records the following changes: · Stream state · Form name · Class name RJE Enhancements Results: - Highly flexible routing of RJE output - Enhanced productivity of users - Improved RJE availability Summary Benefits: - Centralized control in a decentralized, uncontrolled environment - Single point of customer service - Cost reduction · Equipment & Operations - Cost effective use of current equipment - Increased user/operator satisfaction - Cost recovery of centralized equipment - Side benefits · Established large DECnet network · Electronic mail for over 5000 users (up from 300) · Travel savings · Reduced software maintenance