Today’s major organizations still rely on the IBM^® OS/390 mainframe with its integrated Job Entry System ( JES/2 or JES/3 ) and their OS/390 JES based applications. They would like to eliminate the need for existing SDLC WAN networks in order to take advantage of newer multi-protocol communication technologies such as intelligent LAN networks. For such companies, one very real possibility is a solution to migrate Remote Job Entry Services ( RJE ) from SNA or BSC to TCP/IP. This consolidation both simplifies the corporate network communications requirements, and brings all the additional power of more advanced protocols like TCP/IP into use. TPS^®/ JES Services provides this solution.

TPS^®/ JES Services is comprised of two major components: TPS^®/ JES Services Server and TPS^®/ RJS ( Remote JES Services ) Client.

The TPS^®/ JES Services Server operates as an OS/390 component executing in the MVS background in order to make JES/2 and JES/3 available to a TCP/IP based Client. It is brought up as a started task from an APF authorized library since it requires OS/390 APF authorization. The Server first reads the customized configuration file to ensure each Client is given only the access to services they require. This gives complete control to the OS/390 system administrator.

The Server uses the SSI based SAPI interface in conjunction with the SSI based “Extended JES Status” calls to become an “external writer”. These interfaces allow the Server to achieve the same JES status and control as similar JES interfaces to include the ability to act as a “hot writer” automatically processing JES SYSOUT output as it becomes available. The Server also acts as a TCP/IP server for the Client. This Client/Server implementation allows a multitude of simultaneous client connections while only maintaining a single instance of the Server.

The TPS^®/ RJS ( Remote JES Services ) Client operates as a daemon on a UNIX^® or Windows^® System. Each remote Client can be configured to create multiple virtual JES printers uniquely identified by the Client remote ID and printer name. The Client establishes a TCP/IP connection to the Server on the OS/390, and automatically starts downloading any job/printer output. Each virtual printer on the Client can be independently configured to have the JES printer output processed in different ways including being written out as files.

With the addition of JES Services to TPS^®/ NFM ( NetWork File Manager ), the NFM OS/390 client is now capable of reading files directly from the JES output queue. This feature gives an NFM plan the ability to transfer a file directly from the JES output queue to a regular file on any other NFM node. An NFM transfer request from JES will result in the transfer of all JES output that satisfies the criteria specified in the NFM file set parameters for JES.

HIGHLIGHTS

• TCP/IP based for integration with existing company intranet
• Secure key based encryption for all TCP/IP based communications
• Complete OS/390 security preventing unauthorized user access
• Compression for all TCP/IP based communications
• Full JES external writer capability for automatic transport and processing of JES output
• Ability to remotely submit and execute JCL procedures
• Ability to monitor and control the status of JES input and output
• Ability to interactively browse and/or copy JES held job output
• Ability to change JES output disposition including the ability to release held jobs, delete output, and modify and/or redirect the job output
• Diagnostic tools for logging activity, capturing communication traffic, and internet tracing programs
• Optional SSL encryption layer
• ASCII to EBCDIC conversion
• From TPS^® Systems — with 25+ year tradition of excellence in providing network software and support for large global enterprises
  
  
  

FEATURES

• Ability to execute Client utilities in a command line environment, within a customer provided shell script, or by custom front-end software.

Utility Software:

• rjs start
  Command line utility for dynamically starting the TCP/IP connection to the TPS^®/ JES Server. Brings all virtual printers and devices online.
  
• rjs stop
  Command line utility for dynamically stopping the TCP/IP connection to the TPS^®/ JES Server. All current active transfers will be allowed to complete prior to termination.
  
• rjs submit
  Command line utility for transmitting a single file containing JCL text data to be submitted to the JES/2 or JES/3 internal reader for processing. This is the primary method used for starting jobs to run on an OS/390 system.
  
• rjs status
  Command line utility for displaying the status of jobs under the JES subsystem to include jobs waiting for execution, currently executing, or queued for output.
  
• rjs output
  Command line utility for acquiring the output of JES output files. The output can be directed to an output file, a printer, or a custom application for further processing. An additional command line option can be used to indicate whether the file should be deleted after reading, or whether to browse the file and keep it intact.
  
• rjs controls
  Command line utility for changing the current state of JES output files such as deleting job output from the JES queue, releasing a held job, or canceling execution of a currently running job.