1. © 2013 TmaxSoft Co., Ltd. All Rights Reserved.

3. 1. Prerequisite Knowledge 1.1 MVS JCL 1.2 TP-monitor Tmax

4. © 2013 TmaxSoft Co., Ltd. All Rights Reserved.

7. 2. OpenFrame Batch 2.1 OpenFrame Batch Introduction 2.2 OpenFrame Batch Components 2.3 OpenFrame Batch Key Features

8. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 7/40 2.1 OpenFrame Batch Introduction OpenFrame Batch Architecture OpenFrame Batch runs on top of Tmax TP-monitor to leverage Tmax’s load-balancing and failover features. Applications UNIX * WebtoB (Web Server), JEUS (J2EE App Server), RCA (Tmax Raw Client Agent) Third Party Products & Utilities Security TACF OpenFrame/Batch TJES Runner/Spool/Output TSO/E System Utilities Tmax OpenStudio Job Scheduler RDBMS OpenFrame TSAM OpenFrame HiDB OpenFrame NVSM

9. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 8/40 2.1 OpenFrame Batch Introduction OpenFrame Batch Process OpenFrame Batch consists of various components that simulate a mainframe batch environment to run a batch JOB under open environment. Define the JOB Create the JCL Submit the JCL User views output TJES interprets JCL & passes it to Runner TJES collects output & info about the JOB Runner executes the JOB USER ACTIONSSYSTEM ACTIONS System Messages

10. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 9/40 2.2 OpenFrame Batch Components TJES Stands for Tmax Job Entry Subsystem A core component of OpenFrame/Batch. Equivalent to a mainframe’s JES Uses JOBQ/OUTQ/Spool for processing & managing JOBs Supports output processing through a printer & internal reader (JCL submission) Built on top of Tmax TP-monitor in order to support automated error recovery and parallel Sysplex features Runner OpenFrame/Batch module that parses JCL statements and runs an actual JOB System Utilities Various Batch Utilities & Third Party Utilities TSO/E Provides execution of CLIST and interactive processing with the user at a terminal. User Interface TJESMGR (CUI) and OpenStudio (GUI)

11. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 10/40 2.3 OpenFrame Batch Key Features OpenFrame/Batch provides a mainframe JES-compatible environment and powerful batch job management functions. Job management function based on various scheduling policies. Provides an integrated interface for job execution, cancellation, monitoring, and for checking results. Job Management Supports user interactive programs. Supports CLIST scripts. Transmits datasets to and from a PC. TSO/E Equipped with various utilities (IDCAMS, FTP and etc.) Supports various third party utilities Supports EzPlus Supports SORT via various sort engines (ProSort, SyncSort, PowerbSort) Provides Diverse Batch Utilities Supports MVS/JCL, MSP/JCL, and XSP/JCL Provides JCL Analyzer Supports COBOL, PL/1, C, and Shell program JCL Support Multi-node clustering ensures high availability and maximizes system usability Dynamic Job Scheduling for load balancing Spool information sharing Powerful Clustering Function TP-Monitor – based system management Integrated GUI based system admin via OpenStudio Provides spool backup system & catalog information change method. Enhanced Management Function Integration Features Integration with OS authentication. Integration with OpenFrame/TACF to authenticate users & authorize the access to various resources of OpenFrame/Batch. Security Provides real-time I/O count on datasets. Monitoring of and statistics about JOB Supports various logs for analysis Monitoring Features Integration with an external scheduler Initiates batch jobs from online

12. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 3. Job Management 3.1 Introduction 3.2 JOB Flow 3.3 JOB Scheduling 3.4 JOB Group 3.5 JOB Life Cycle 3.6 Internal Reader 3.7 Runner 3.8 TEXTRUN 3.9 TJES Servers 3.10 SPOOL

13. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 12/40 3.1 Introduction TJES Components TJES Engine -Consists of Tmax servers that control & monitor batch JOBs. -Manages & prints out outputs. Runner -Parses JCL statements and executes programs specified in the JCL. TEXTRUN -Integrates with external, third party JOB scheduler (Control-M). -Submits a JOB and retrieves its result. INTRDR -A module that can submit a JCL stream (used by OUTPUT processing server). -Used for executing a batch JOB from an online application. TJESMGR -Command-line based user interface that allow users to manage JOBs. What is TJES (Tmax Job Entry Subsystem)? 1.Receives JOBs in a form of JCL 2.Schedules JOBs for processing 3.Controls JOB output processing

14. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 13/40 3.1 Introduction 3.1.1 TJES Architecture Diagram

15. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 14/40 3.2 JOB Flow OpenFrame Servers in Master Node OpenFrame Servers in Each Node OF server User Interface Process JCL Runner ofrsasvrofrlmsvr obmjmsvr obmjhist JOBQ 1. Job submit 2. Authentication 3. Insert job info. into JOBQ 10. Request printing 4. Request scheduling obmjschd 5. Request run 7. Execute runner 11. Signal terminated obmjinit 9. Dataset Lock / UnLock 8. Update job as working 6. Assign a job to a runner 13. Clear the runner slot 14. Report done Request logging 12. Update job as finished shared memory (Runner Info)

16. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 15/40 3.2 JOB Flow OF server Process Library OpenFrame TJES User Interface ofrsasvr obmjschdobmjhist obmjinit obmjmsvr JCL runner Macro parser JCL parser ofrcmsvr tconmgr 1. Macro Submit5. Expanded JCL parsing 6. Authentication 7. JOB scheduling … 2. Macro parsing 3. Wait for a reply 4. Request a reply & Reply a request 3.2.1 Macro Expand in TJES (XSP)

17. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 16/40 3.3 JOB Scheduling (MVS, MSP) TJES Scheduling Policy Priority based Scheduling -The JOB with the highest priority is scheduled first (if a runner is available). -If multiple JOBs have the same priority, the JOBs are executed based on the order they were submitted. Priority Aging -JOB priority may increase at regular intervals while the JOB is awaiting execution. Node Affinity -Specify the Node where the JOB must be executed. Matching Class of JOB and Runner -A runner can have multiple classes (up to 8) Check JOBNAME duplicates -JOBs with duplicate JOBNAMEs cannot run simultaneously (in Working or Suspended) (optional). Check Runner Status -A JOB can be assigned only if a runner is in ACTIVE status.

18. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 17/40 3.3 JOB Scheduling (XSP) TJES Scheduling Policy in XSP Checks system multiplicity -In XSP, system multiplicity limits the number of jobs that can run simultaneously. JOB Group level Scheduling -In XSP, a JOB group is selected. Next, a JOB in the JOB group is scheduled. -Priority based scheduling -Only when no JOBs in higher JOB Groups can be scheduled, JOB Groups with lower priority can be scheduled. JOB level Scheduling -JOB level scheduling is affected by JOB group attributes (REL, Multiplicity). -Checks JOB Group Multiplicity -If REL == ‘Y’, JOBs are scheduled in first come first served order. If a JOB is in HOLD, the JOB group is also held. -If REL == ‘N’, JOB is scheduled by priority order. (submitted order in same priority) -Priority Aging -Node Affinity -Check JOBNAME duplicates -Checks runner status

19. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 18/40 3.4 JOB Group (XSP) JOB Group In XSP, a JOB must be contained in a JOB Group (default: SYSGRP). Attributes of JOB Group -Multiplicity: the number of jobs executed concurrently. -REL: sequential scheduling of JOBs in the JOB group -Priority: JOB group priority. Used by scheduler -JOB default parameter: default parameter of the JOB in the JOB group. -WAIT: scheduling of the JOB group is postponed until -Time -Operator response -Data completion -The end of the other JOB Group

20. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 19/40 3.5 JOB Life Cycle JOB StatusDescription READY Internal status during submission (intermediate status) START JOB has been submitted but has not been allocated to a region HOLDJOB has been submitted as TYPRUN=HOLD WORKING JOB is currently being executed by JCL Runner JOB can be paused using the SUSPEND command SUSPEND State when a running JOB is suspended by a user JOB can resume using the RESUME command DONE JOB successfully completed Result satisfies the condition ERROR JOB successfully completed Result does not satisfy the condition STOPJOB is stopped by a user FLUSH JOB cannot complete due to an error (JCL runtime parsing error, dataset related error or system error)

21. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 20/40 3.6 Internal Reader Internal Reader Internal Reader is special device that submits a JCL stream. Ofrpmsvr (output processing server) uses Internal Reader to submit the output that is JCL. -Output of batch job -Output of online transaction Example: //ddname DD SYSOUT=(oclass,INTRDR)

22. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 21/40 3.7 Runner Role of Runner Prepares dataset resources Verifies resource authorization Prevents any access conflicts using lock server Sequentially executes program(s) specified in STEP Checks for the JOB failure condition

23. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 22/40 3.7 Runner Process (MVS) obmjinit tjclrun JCL parser (Library) Parsing JCL Procedure Internal Utility FTPIDCAMS DSNTIAULIEBGENER External Utility SortFastUnload FactSqlLoader Application Business Module (EXE) PGMRTS00 Business Module (Shared Object) CALL EXEC PGM EXEC PROC Run each step in job : fork 3.7.1 Runner Process

24. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 23/40 3.7 Runner Process interacted with AIM and Macro Expand in Procedure (MSP) obmjinit tjclrun Parsing Internal Utility FTPIDCAMS DSNTIAULIEBGENER External Utility SortFastUnload FactSqlLoader EXEC PROC Run each step in job: fork JCL Macro parser (Library) JCL JCL parser (Library) Parsing Procedure Expanded Procedure Application OSAMFRUN JXGIJSM Application server Business Module (Shared Object) Business Module (Shared Library) Business Module (Shared Library) Business Module (Shared Object) EXEC PGM or PGM Using PED (Message File) EXEC PGM Using PED (Presentation File) CALL 3.7.1 Runner Process

25. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 24/40 3.7 Runner Process interacted with AIM (XSP) obmjinit tjclrun Parsing Internal Utility FCHKKQCAMS FCPYFDLT External Utility SortFastUnload FactSqlLoader Run each step in job: fork JCL Application OSAMFRUN JXGIJSM Application server Business Module (Shared Object) Business Module (Shared Library) Business Module (Shared Library) Business Module (Shared Object) EXEC PGM or PGM Using PED (Message File) EXEC PGM Using PED (Presentation File) CALL 3.7.1 Runner Process

26. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 25/40 3.7 Runner Changing User in Runner Case 1 Runner External Utility 1. STOP JOB 3. Kill child process Can kill child process because of root authority Runner External Utility 1. STOP JOB2. Kill child process Cannot kill child process when a Utility was executed by a different user Runner Running with authority of normal user Running with authority of super user (root) 3.7.2 Runner Internal 2. Acquire Superuser Privilege 4. Return to normal User

27. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 26/40 3.7 Runner Changing User in Runner Case 2 Runner DataSet FILE Utility or Application with authorized user Runner Can access resource because PGM has permission 1. EXEC PGM (fork) 3. Use Resource DataSet FILE Utility or Application Running with non-authorized user Running with authorized user 1. EXEC PGM (fork) 2. Use Resource Cannot access resource when the executed PGM does not have permission 3.7.2 Runner Internal 2. Change to authorized user

28. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 27/40 3.8 TEXTRUN TEXTRUN process Third party JOB scheduler executes TEXTRUN with JCL script TEXTRUN submits JCL TJES executes Runner with JCL TEXTRUN is monitoring until JOB ends TEXTRUN returns the JOB return code Third party JOB scheduler checks the return code and determines whether scheduling will continue or stop Restriction: TEXTRUN is monitoring only one JOB. JCL script must contain just one JOB. TEXTRUNTJCLRUN Third party Scheduler TJES obmjmsvrobmjinit 1. Invoke with JCL 5. Return with return code 2. Submit JCL 4. Monitoring JOB and Get result 3. Execute JCL

29. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 28/40 3.9 TJES Servers FunctionalityNameDescriptionTypeInstanceResources Managing JOB obmjmsvr Submits a JOB Removes a JOB Provides information about JOBs Manages the output of JOBs TCS Many / Node VSAM Scheduling JOB obmjschd Issues a unique JOBID to the newly submitted JOB Schedules JOBs in the START status to runners Changes scheduling properties (class, status) of a JOB Supports multiple runner classes Boots and Shuts down TJES nodes (obmjinit) UCS One / Domain VSAM Executing JOB obmjinit Invokes Runner to execute the scheduled JOB. Manages working JOBs (suspend, resume, stop) Manages runners (classes, status) Monitors JOB status changes and updates JOBQ. Boots and shuts down a TJES node (itself) UCSOne / Node VSAM/ Shared Memory Loggingobmjhist Logs TJES operations (JOB status changes, commands issued) TCS One / Domain N.A

30. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 29/40 3.10 SPOOL SPOOL Dataset INPJCL -A replica of the submitted JCL JESMSG -The execution information of JOB’s steps JESJCL -A parsed tree of the submitted JCL SYSMSG -A system message from TJCLRUN during JOB execution CATPROC -A cataloged procedure in the submitted JCL OUTPUT DATA -A output data defined by SYSOUT DD What is SPOOL? 1.Special Dataset used by TJES 2.Stores internal data of TJES and outputs data 3.Backed up and restored by TJESMGR

31. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 4. TSO/CLIST 4.1 TSO/E & CLIST

32. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 31/40 4.1 TSO/E & CLIST Execution of CLIST at a terminal OpenFrame system Service Routine IPF module OpenFrame module DataSetSpool Perlclistrun XSUB PC with OpenFrame file transfer module UNIX terminal 1. Exec CLIST 4. Exec Perl 3. converting2. Parsing CLST ScriptsPerl Scripts Interactive processing with user Receive the request and data from user at the terminal Transmit dataset to and from PC Flow of control Flow of data

33. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 5. Features 5.1 Security Feature 5.2 Multi-Node Environment 5.3 Failover

34. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 33/40 5.1 Security Features TACF structure and control flow. ①② ④ ⑤ ⑥⑦ ⑧ OpenFrame ③ Resource Manager Tx. Data Set Etc. TACF Auth. Server TACF API TACF Repository Resources resource User request for resource access Send the request to TACF (RM) Authentication and access control information check Check access authority for the resource Grant or reject the resource access Return the result of the service request 5.1.1 TACF - Structure and control flow

35. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 34/40 5.1 Security Features User Authentication - A user ID allows a user to be recognized. A user password confirms the user ID is valid. Only users with a valid user ID and password are able to access the system. Resource Access Control - Resource Access Control protect system resources from being used by unauthorized users. Logging-in to Access Resources - The TACF records the daily log history of user logins and resource access based on the resource access level. - These log records are used as the source data for statistical reports and analysis of resource usage and user behavior. 5.1.1 TACF – Key Functions

36. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 35/40 5.1 Security Features Provides various interfaces The TACF provides a Tmax based interface and an API type interface to meet customer security requirements as well as the needs of a unique customer environment. Flexible auditing level configuration The TACF can adjust the audit-level and generate log files for each resource access. Thus only specified log items remain and the overall log-overhead is reduced. Real-time resource management The TACF enables real-time resource management so system administrators can limit the use of resources by time and for every user. Memory caching The TACF’s memory caching feature minimizes the load on the DB. When cached information is modified, the caching memory is synchronized. 5.1.1 TACF – Key Features

37. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 36/40 5.1 Security Features Security in TJES With OS account authentication -JCL userid and password are verified. Integrated with TACF (Tmax Access Control Facility) -JCL userid and password are verified. -Surrogate submission is supported. -JOBNAME authorization check in JOB management is supported. -Submit, Start, Hold, Cancel, Stop, Suspend, Resume, and Remove a job. -View a Spool. 5.1.2 Security in TJES

38. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 37/40 5.2 Multi-node Environment OpenFrame Batch engine supports Multi-Node clustering to provide the necessary performance and stability for batch JOB processing. NODE BNODE A UTILITYDATASET MANAGEMENT LIBRARYTJESMGRUTILITYDATASET MANAGEMENT LIBRARYTJESMGR 1 / Domain Server (BASE) Many / Node Server One / Node Server Batch Process Library or Utility1 / Domain Server (TJES) OBMJMSVR JCL RUNNER OBMJINIT OFRUISVROFRDSEDT Shared Memory - Runner Info - Running JOB Info Tmax JCL RUNNER OBMJMSVR JCL RUNNER OBMJINIT OFRUISVROFRDSEDT Shared Memory Runner Info - Running JOB Info Tmax JCL RUNNER OFRLMSVR OFRSASVR OBMJSCHD OBMJHIST OFRPMSVR OBMJSPBK OFRCMSVR OFRDMSVR OFRSMLOG OBMJHIST OBMJSPBK OpenFrame/TSAM Control-M TJESEXTRUN OpenStudio/ Master-Agent OpenStudio Console TS 0 System MetaData TACF Authentication Information TS 1 MCAT VVDS VOL 1 UCAT TS 2 JOBQ VVDS VOL 2 TS 3 TSQ VVDS VOL 3 TS 4 VVDS VOL 4 ~ 12 LOCK OUTPUTQ DATASET SDS PDS GDGsSPOOL Shared Disk

39. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 38/40 5.3 Failover TJES provides the following failover mechanisms based on Tmax TP-monitor: 1.TJES Level Failover – Reconnects to TSAM, tries to update the JOB status, and stops all executing jobs while obmjinit restarts 2.Server Level Failover – TMM (Tmax Management Server) automatically restarts processes that failed 3.Node Level Failover – A backup server automatically takes over when a failure occurs. The Node Level Failover is based on Tmax Multi-Node failover mechanism 4.DB Connection Failover – Switches to the backup connection when the primary DB connection fails

40. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 39/40 5.3 Failover Server Level Failover Server FailureServer Restart obmjinit CLLTMM CLH obmjsvr obmjhistobmjschdofrsasvr obmpmsvr obmjinit CLLTMM CLH obmjsvr obmjhistobmjschdofrsasvr obmpmsvr

41. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 40/40 5.3 Failover Node Level Failover Before Failure After Failure Node 1 Critical Server Batch Server Node 2 Batch Server Data Node 1 Batch Server Node 2 Batch Server Data Critical Server Automatic Loading Network Failure Automatic reconnection

42. © 2013 TmaxSoft Co., Ltd. All Rights Reserved. 41/40 Thank you TmaxSoft Co., Ltd