tivoli workload scheduler extended...

Tivoli Workload Scheduler ExtendedAgent for MVS and OS/390 User’sGuideClient (CD) 1.4.4 / Host (Tape) 1.4.3

Tivoli Workload Scheduler Extended Agent for MVS and OS390 (May 2000)

Copyright Notice

Copyright © 2000 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved.May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBMCustomer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical,chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended forproduction and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimedincluding the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, TivoliManagement Environment, and TME 10.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open CompanyLimited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will beavailable in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services isnot intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to TivoliSystems’ or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program,or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation inconjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of theuser.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to theIBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Platform-specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation on TWS UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installation on TWS-Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installation on MVS and OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Additional Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

MVS Gateway Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Set Up and Operation . . . . . . . . . . . . . . . . . . . . . . . . 11Defining an MVS and OS/390 Extended Agent Workstation . . . . . . . . . . . . . 11

Command Line Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Method Options Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Using a Method Multiple Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Defining Jobs in MVS and OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Defining MVS and OS/390 Jobs in Workload Scheduler (TWS) . . . . . . . . . . 19

Command Line Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Script File Syntax for TWS-Scheduled MVS Jobs . . . . . . . . . . . . . . . . 26

iiiTivoli Workload Scheduler Extended Agent for MVS and OS/390 User’s Guide

Syntax for MVS and OS/390 Job Dependencies . . . . . . . . . . . . . . . . . . 28

Scheduling MVS and OS/390 Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 3. Reference Information . . . . . . . . . . . . . . . . . . . . . . . 33Technical Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Operation with JES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Operation with CA7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Other CA7 Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Operation with OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Checking for Files on MVS and OS/390OS/390. . . . . . . . . . . . . . . . . . 38

Timing Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Gateway Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

iv Client (CD) 1.4.4 / Host (Tape) 1.4.3

Preface

The Tivoli Workload Scheduler Extended Agent for MVS and OS390User’s Guideprovides task-oriented information on how to set up anduse Workload Scheduler to control and execute MVS and OS390jobs.

Who Should Read This GuideThe target audience for this guide is system administrators andmanagers who set up and use Tivoli Workload Scheduler to controlMVS and OS390 jobs. Users of the guide should have someknowledge of:

¶ The Workload Scheduler application

¶ The MVSand OS390 environment

Prerequisite and Related DocumentsThe following related documentation:

¶ Tivoli Workload Scheduler User’s Guide

Provides information about using Tivoli Workload Scheduler tomonitor and manage your job scheduling environment.

What This Guide ContainsThis guide includes illustrations of screens and descriptions for boththe Legacy GUI and the JS Console GUI. The Tivoli WorkloadScheduler Extended Agent for MVS and OS390 User’s Guidecontains the following sections:

¶ Chapter 1, “Introduction”

Describes how to install the product.

¶ Chapter 2, “Setup and Operation”

Describes how to setup Extended Agent workstations, jobs andjob streams.

¶ Chapter 3, “Reference Information”

vTivoli Workload Scheduler Extended Agent for MVS and OS/390 User’s Guide

Provides a technical overview of job states when working withJES, CA7, or OPC in the TWS environment.

Conventions Used in This GuideThe guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, file names, or other information thatyou must use literally appear in bold. Names of windows,dialogs, and other controls also appear in bold.

Italics Variables and values that you must provide appear in italics.

MonospaceCode examples appear in monospace format.

Platform-specific InformationThe following table identifies text used to indicate platform-specificinformation or procedures.

Text Supported Platform

AIX 4.x IBM RS/6000 series running AIX 4.2 or 4.3

DG/UX Data General AViiON series running DG/UXR4.20MU04 on the ix86 platform

HP-UX 10.20 and11.0

HP9000/700 and 800 series running HP-UX 10.20and 11.0

SGI SGI IRIX versions 6.5

NCR NCR 3000 series running NCR UNIX SVR4MP-RAS 3.00 and 3.01

DEC Unix OSF1 4.OD and 4.0F

SINIX Pyramid 5.4.4 and 5.4.5

Sequent Sequent DYNIX 4.4.x and 4.5.1

SCO UnixWare 7.1.0

Solaris Sun SPARC series running Solaris 2.6 and 2.7

NCR SVR4 MP-RAS V3.02 UNIX

vi Client (CD) 1.4.4 / Host (Tape) 1.4.3

Text Supported Platform

Windows andWindows NT

Windows 2000 (Only for the JS Console) Client,serve, agent: Windows NT 4.0 SP4 or higher

Contacting Customer SupportIf you encounter difficulties with any Tivoli products, you can enterhttp://www.support.tivoli.com to view the Tivoli Support home page.After you link to and submit the customer registration form, you willbe able to access many customer support services on the Web.

Use the following phone numbers to contact customer support in theUnited States: the Tivoli number is 1-800-848-6548(1-800-TIVOLI8) and the IBM number is 1-800-235-5511 (press orsay 8 after you reach this number). Both of these numbers directyour call to the Tivoli Customer Support Call Center.

We are very interested in hearing from you about your experiencewith Tivoli products and documentation. We welcome yoursuggestions for improvements. If you have comments or suggestionsabout this documentation, please send e-mail to [email protected].

You can also contact Tivoli at the following addresses:

Company home page.http://www.tivoli.com

Support home page.http://www.support.tivoli.com

E-mail address for technical [email protected]

E-mail address for documentation [email protected]

viiTivoli Workload Scheduler Extended Agent for MVS and OS/390 User’s Guide

viii Client (CD) 1.4.4 / Host (Tape) 1.4.3

Introduction

The Tivoli Workload Scheduler (TWS) Extended Agent for MVSand OS/390 gives you the ability to schedule and control MVS andOS/390 jobs using TWS’s sophisticated job scheduling features.

Features¶ Use TWS’s scheduling functions to schedule MVS and OS/390

jobs to run at specific times and in a prescribed order.

¶ Define dependencies between TWS launched jobs running ondifferent systems and platforms, including MVS and OS/390,UNIX, Windows NT, HP 3000, and SAP R/3.

¶ Define dependencies for TWS-launched jobs based on thecompletion of MVS and OS/390 jobs that were not launched byTWS.

¶ Define dependencies for TWS-launched jobs based on theexistence of files on an MVS and OS/390 system.

1

1Tivoli Workload Scheduler Extended Agent for MVS and OS/390 User’s Guide

1.In

trod

uctio

n

Software RequirementsThe Extended Agent for MVS requires the following softwareversions:

Software Requirements Versions

TWS Versions: Maestro 5.2, 6.x and TWS 70. Note:Use version 1.4.4 for Client (CD) or1.4.3 for Host (Tape).

Operating System: MVS/ESA V5.2 OS/390 1.3 andabove. Note: Use the most recentrelease (1.4.6) if you are running onOS/390 2.5 and above.

TCP/IP version: One of the following: IBM 3.1 orhigher Interlink 3.1 or higher OpenConnect 2.3 or higher

Job Scheduling Interface: One of the following: JES2 or JES3OPC 1.3.1 or higher

InstallationThe Extended Agent for MVS and OS/390 software consists of theMVS- methods that reside on the TWS host, and MVS gatewaysoftware that resides on MVS and OS/390. The MVS gatewaysoftware is installed separately from a 3480 tape cartridge.

Installation on TWS UNIXThe TWS-MVS methods are delivered as tar files on CD. Followthese steps to install them:

1. Stop TWS on the host workstation.

2. Log in as root, and change your directory to twshome.

3. Mount the installation CD, and restore the tar file:tar xvf cd_folder/TWS/platform/MVS.TAR

Software Requirements

2 Client (CD) 1.4.4 / Host (Tape) 1.4.3

where:

tar parameter Description

cd_folder The pathname of your CD drive or folder.

platform The target platform from the list below.

HPUX Hewlett-Packard AIX IBM MIPS MIPS-basedINTEL Intel-based SOLARIS Sun Solaris SUNOSSunOS DGUX Data General UNIX DECUX DigitalUNIX

4. Execute customize as follows:/bin/sh customize -update -uname[user’s name]

5. With conman or gconman, start TWS on the host workstation.After installation, you can obtain version information about thesoftware using the version command. For example:version -f twshome/methods/version.info

Installation on TWS-Windows NTThe TWS-MVS methods are delivered on CD. Follow these steps toinstall them:

1. Stop TWS on the host workstation.

2. Log in as a user in the Administrators group or the DomainAdministrators group, as appropriate.

3. Close any open Windows applications, including the FileManager.

4. Insert the CD and copy the files to TWS’s methods directory.For example, if TWS is installed in C:\WIN32APP\maestro, andthe CD drive is D:, enter:COPY D:\MAESTRO\I386NT\*.* C:\WIN32APP\MAESTRO\METHODS

5. Run the Setup program. For example, if TWS is installed inC:\WIN32APP\MAESTRO, enter:C:\WIN32APP\MAESTRO\SETUP\SETUP.EXE

a. On the Welcome screen, click Next.

Installation


1.In

trod

uctio

n

b. On the Account Information screen, enter the account nameand password and click Next.

c. On the Setup Information screen, verify the information youentered and click Next.

d. A message informs you that TWS is being customized. Whenthe ″Workload Scheduler has been installed″ messageappears, click OK.

6. Start TWS on the host workstation.

Installation on MVS and OS/390The MVS and OS/390 gateway module is delivered on a 3480 tapecartridge, written using the non-IDRC (uncompressed) format. Thetape contains two files: the control library and the load library.

Unload the Files1. Modify and submit the following JCL to unload the tape. Make

these changes, where applicable:

¶ Enter an appropriate job name.

¶ Identify a 3480 tape device.

¶ XXXXXXXX can be any high level qualifier//JOBCARD JOB 1, /* EDIT */// CLASS= , /* EDIT */// MSGCLASS= , /* EDIT */// NOTIFY=YOURID, /* EDIT */// REGION=4096K/*JOBPARM LINE=9999

//*//REST PROC 01=,UNIT=,VOLSER=,TAPE=

//*//CNTL EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//INPUT DD DSN=UNISON.CNTL,DISP=SHR,UNIT=&TAPE,// VOL=(,RETAIN,SER=UNISON),// LABEL=(1,SL,EXPDT=98000)//OUTPUT DD DSN=&01..UNISON.CNTL,UNIT=&UNIT,// VOL=SER=&VOLSER,// DISP=(NEW,CATLG,DELETE),// SPACE=(TRK,(4,1,45))//*

Installation


//LOADLIB EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//INPUT DD DSN=UNISON.LOADLIB,DISP=SHR,

UNIT=&TAPE,// VOL=(,RETAIN,SER=UNISON),// LABEL=(2,SL,EXPDT=98000)//OUTPUT DD DSN=&01..UNISON.LOADLIB,UNIT=&UNIT,// VOL=SER=&VOLSER,// DISP=(NEW,CATLG,DELETE),// SPACE=(CYL,(3,1,45))//*// PEND//*//STEP1EXEC REST,TAPE=’CART’, /* 3480 TAPE DRIVE/*// UNIT=DISK,// VOLSER=,// 01=’XXXXXXXX’//CNTL.SYSIN DD *C I=INPUT,O=OUTPUT//LOADLIB.SYSIN DD *C I=INPUT,O=OUTPUT//

2. Authorize the load library. This can be done with SETPROG. Forexample:SETPROG APF,ADD,DSN=YOURID.UNISON.LOADLIB,

VOL=xxxxxx

where: xxxxxxx is the volume serial number where the loadlibrary is located. or:SETPROG APF,ADD,DSN=YOURID.UNISON.LOADLIB,VOL=SMS

which indicates a volume under control of SMS.

Installation OverviewThe two MVS program components of TWS’s MVS gateway are:

TSITCP02This program establishes that TWS is tracking on the MVSsystem. The program is started by the TSDSPACE job.

TSITCP00This is the “gateway” program that manages TCP/IPcommunications between TWS and the MVS system. It isstarted by the TSSERVER job. TSITCP00 translates

Installation


1.In

trod

uctio

n

Workload Scheduler commands to MVS equivalents, routesMVS information back to TWS, and performsEBCDIC-ASCII data conversions.

Both of the programs run as started tasks, with a TIME=NOLIMITparameter. TSITCP02 is always started first, followed by TSITCP00.If the programs must be terminated for any reason, they should bestopped, not cancelled, to ensure that they shut down gracefullywithout impacting other programs that use the IEFU84 Exit.

Additional Notes

IEFU84 ExitThe Extended Agent for MVS tracks job streams using the IEFU84exit. This exit must be turned on in the SMF parm member inSYS1.PARMLIB. IBM distributes a dummy IEFU84 exit with theoperating system that is an IEFBR14 program. The TSDSPACE job(discussed later) will dynamically chain to the IEFU84 exit. If theIEFU84 exit is currently being used, TSDSPACE will “front-end”the IEFU84 exit, obtain the information it requires, and then branchto the existing user exit(s). When TSDSPACE is terminated, itremoves itself from the chain and restores the chain to its originalstatus. It is important to note that TSDSPACE has no effect on theexisting IEFU84 exit(s), which will continue to run normally.

SecuritySecurity is enforced in several areas, usually, RACF, TOP SECRET,ACF2, etc. The TSSERVER job (discussed later) should have theability to submit jobs that run under the userids that are supplied inthe JCL to be submitted. The JCL should not contain passwords.This can be authorized using SURROGAT class resources in RACF,and the equivalents in ACF2 and Top Secret. PROPCNTL classresources in RACF should be used to prevent submitted jobs fromrunning under the TSSERVER userid. ACF2 and Top Secretequivalents should also be used. Resource class JESJOBS in RACF,and ACF2 or Top Secret equivalents, can be used to control whichjob names and userids (with or without passwords) can be submittedby TSSERVER.

Installation


Note that TWS does not support the use of CA-7 security.

Console SecurityThe TSSERVER job (discussed later) obtains an extended MVS andOS/390 console when displaying job streams and issuing modifycommands to CA-7. It must have the authority to use an extendedconsole. See your security administrator to ensure that this is thecase. Note that CA-7 must be configured to allow users to issuemodify commands through the master or extended consoles.OPERCMDS should be modified to allow for this functionality if itis not already allowed. See also “SYSTSIN Variables” on page 8 forinformation about specifying a user ID of authority.

Note that Unison recommends the use of external security (seeSecurity above) to authorize the CA-7 user specified forTSSERVER, since Workload Scheduler does not support providing apassword with the user name.

Start Up

Note: TSDSPACE must be up before TSSERVER is started. Toshutdown, shutdown TSSERVER first before shutting downTSDSPACE.

Create and submit the following JCL, called TSDSPACE, to start theExtended Agent Data Space. It is recommended that this job be astarted task, rather than a submitted job stream. It is important thatthe job not be canceled

TSDSPACE will create the Data Space and install the IEFU84 exit.Add TSITCP00 to the AUTHCMD NAMES section ofSYS1.PARMLIB member IKJTSOxx, where xx is the member inwhich the change is made. Create and execute the following as astarted task://TSSERVER PROC MEMBER=TSPARMS,// VERSION=V1R3M0//IEFPROC EXEC PGM=IKJEFT01,// PARM=TSITCP00,// REGION=4M,// TIME=NOLIMIT//STEPLIB DD DISP=SHR,DSN=SYS1.UNISON.&VERSION.LOAD

Installation


1.In

trod

uctio

n

// DD DISP=SHR,DSN=SYS1.SEZATCP//SYSTSIN DD DISP=SHR,DSN=P390.UNISON.CNTL(&MEMBER)

//SYSTSPRT DD SYSOUT=*

See SYSTSIN Variables below for a description of the parametersettings.

To terminate the job, issue a stop from any MVS console. Forexample: STOP TSSERVER

Note: EQQ only pertains to OPC and not to CA7 or JES. All DDstatements can be commented out if you are not usingOPC.After installing the MVS or OS/390 gateway do arefresh or IPL on the MVS system to activate the changes.

SYSTSIN VariablesThe SYSTSIN variables are described below. You can modify thesettings as required for your site configuration. The default settingsare in parenthesis.

Variable Description

CA7NAME(CA7ONL) The name of the CA-7 control region address space.Ignored if CA-7 is not used.

CA7USER(CA7CNSL) The userid that is used to issue CA-7 commands.Ignored if CA-7 is not used.

DEBUG(NO) If set to YES, it causes the MVS gateway to outputdiagnostic messages. Use only in coordination withUnison Technical Support.

INTERLINKSUBSYSTEM(ACSS) The name of the subsystem used by Interlink TCPIPstack. Ignored if Interlink is not used as TCPIPstack.

MAXWAIT(500) The maximum amount of time, in hundredths of asecond, to wait for a response to commands. Do notset it above 500.

MCSSTORAGE(3) The amount of storage, in megabytes, used by eachextended console used by the MVS gateway.

Installation



OPCMSGCLASS(*) The message class for the dynamically allocatedmessage logs used by OPC. The asterisk causes theclass to be set the same as TSSERVER. Ignored ifOPC is not used.

OPCSUBSYSTEM(OPCS) The subsystem name used for communications withthe OPC control region.

PEERADDRESS(0 0 0 0) The default, 0.0.0.0, permits access by any host. Forbetter security, enter the IP address of the WorkloadScheduler host of the MVS x-agent. Note: Do notinclude the ″.″ (period) between the 0’s in yourcode. The periods will show up in the display!

PORT(5000) The TCP port number used by TWS and the MVSgateway for communications. This must be the sameas the value entered in the TCP Address field of theMVS x-agent workstation definition.

PUTLINE(YES) When set to YES, it directs trace information toDDNAME SYSTSPRT.

QLIMIT(2000) The maximum number of messages to be queued toan extended console.

SUBSYS(UNIS) The prefix used by the Extended Agent for MVS asthe first four characters of extended console names.It is also used as the first four characters of internalreader DDNAMES. Change only in coordinationwith Unison Technical Support.

SVCDUMP(NO) When set to YES, abends will cause an SVC dump.Use only in coordination with Unison TechnicalSupport.

TCPNAME(TCPIP) The name of the TCPIP address space when theIBM version of TCPIP stack is used.

TCPIPSTACK(IBM) The vendor of TCPIP stack (IBM, INTERLINK orOPENCONNECT).

TERMINATOR(X’25’) The transaction termination character. Do not changethe default unless directed to do so by UnisonTechnical Support.

Installation


1.In

trod

uctio

n


WTP(NO) When set to YES, it directs trace information toSYSLOG as write-to-programmer information. Thiscan be used if SYSTSPRT does not suit your needs.

MVS Gateway VersionThe version of TSSERVER (and TSDSPACE) appears in the firstline of the TSSERVER log. For example:TSITCP10 VERSION RELEASE MODIFICATION LEVEL = V1R4M3

where V1R4M3 contains version, release, and modification levels.

Installation


Set Up and Operation

Tivoli Workload Scheduler (TWS) launches jobs on an extendedagent for MVS and OS/390 workstation. The Extended Agent forMVS and OS/390 is defined in a standard TWS workstationdefinition, which gives it a name and identifies the access method tobe used. The Extended Agent for MVS and OS/390 workstation is aworkstation definition linked to an instance of OS/390 Host.

To launch a job on an Extended Agent for MVS and OS/390workstation, the TWS host executes the access method, passing itinformation about the job. The access method communicates withthe instance of OS/390 Host and monitors the job throughcompletion, writing job progress and status information to the job’sstandard list file.

Defining an MVS and OS/390 Extended AgentWorkstation

Extended Agent for MVS and OS/390 workstation definitions arerequired for each MVS and OS/390 entity through which TWS willschedule and launch jobs. They are defined in the standard mannerand include the name of the x-agent’s host and the method name.

Both the legacy GUI and JS Console (newer) GUI screens areillustrated in this chapter. Figure 1 shows the legacy GUI,gcomposer workstation (cpu) Definition window for an ExtendedAgent for MVS and OS/390 named mvs2. For information aboutusing gcomposer, refer to the Tivoli Workload Scheduler User’s

2


2.S

etU

pan

dO

peratio

n

Guide. Figure 2 shows JS Console MVSCPU workstation definitionin the ″Properties - Workstation in Database″ window.

Fields in the CPU Definition window are described in the followingtable:

Field Description

Legacy GUI

Node: The node name or IP address of the MVS system. Thiscan be the same for more than one Extended Agent forMVS.

TCP Address: The TCP address (port number) of the MVS gateway onthe MVS system. Enter the same value as the PORTparameter described in the SYSTSIN variable table inChapter 1.

OperatingSystem:

Select OTHER.

Figure 1. Defining a Workstation (Legacy GUI)

Defining an MVS and OS/390 Extended Agent Workstation


Field Description

Description: An optional free-form textual description of theworkstation (up to 40 characters).

ResolveDependencies

Not used.

Full Status Not used.

AUTO Link Not used.

Ignore Select if you want TWS to ignore this workstationdefinition.

Server: Not used.

Host CPU: The TWS name of the Extended Agent for MVS’s host.This is the TWS master, a fault-tolerant agent, or astandard agent.

Access: The name of the MVS access method executed by theTWS host (see Host CPU or Host above). The methodsare as shown for the JS Console GUI.

Access orAccessMethod:

The name of the MVS access method that is executed bythe TWS host (see Host CPU or Host above). Themethods are:

mvsca7Launch and monitor MVS jobs via CA-7.

mvsjes Launch and monitor MVS jobs via JES2 orJES3.

mvsopc Launch and monitor MVS jobs via OPC.



2.S

etU

pan

dO

peratio

n

Fields in the Properties - Workstation in Database (WorkstationDefintion) window are described in the following table:

Field Description

JS ConsoleGUI

Name: The TWS workstation name of the Extended Agent forMVS.

Node: The node name or IP address of the MVS system. Thiscan be the same for more than one Extended Agent forMVS. (Appears in the JS Console Only)

Figure 2. Defining a Workstation (JS Console GUI)



Field Description

TCP Port: The TCP address (port number) of the MVS gateway onthe MVS system. Enter the same value as the PORTparameter described in the SYSTSIN variable table inChapter 1.

OperatingSystem:

Select OTHER.

Domain Use the default Masterdm.

Time Zone Used to set the required time zone.

Description: An optional free-form textual description of theworkstation (up to 40 characters).

WorkstationType:

Select Extended Agent. (JS Console GUI only)

ResolveDependencies

Not used.

Full Status Not used.

AUTO Link Not used.

Ignore Select if you want TWS to ignore this workstationdefinition.

Server: Not used.

Host: The TWS name of the Extended Agent for MVS’s host.This is the TWS master, a fault-tolerant agent, or astandard agent.

Access orAccess Method:

The name of the MVS access method that is executedby the TWS host (see Host CPU or Host above). Themethods are:

mvsca7Launch and monitor MVS jobs via CA-7.

mvsjes Launch and monitor MVS jobs via JES2 orJES3.

mvsopc Launch and monitor MVS jobs via OPC.

Procedure to Create a Workstation Using the Legacy GUI: Todefine an MVS and OS/390 Extended Agent Workstation on thelegacy GUI, follow these steps:



2.S

etU

pan

dO

peratio

n

1. Run the TWS Composer and select CPU.

2. Right click to bring up the system menu and select “Create NewWorkstation”. Enter the CPU name.

3. In the CPU Definition Screen, enter your data in the fields.Enter your node, tcp port. Select your operating system. Enter adescription (optional). select a domain. In the TWS Optionssection, select “Extended Agent”. Enter the host cpu and selectthe desired access method. Click on OK. Select FILE > SAVEand close this window.

Procedure to Create a Workstation Using the JS Console GUI:To define an MVS and OS/390 Extended Agent New Workstation onthe newer JS Console GUI, follow these steps:

1. From the main JS Console window, either from the top toolbar,select the “New Workstation” icon and follow from step 2 below,or from the main JS Console window right click on TWS7.0 andselect “New Workstation” from the drop down menu.

2. In the Properties screen, complete the fields: Workstation Name,Node (host or IP address), and TCP port

3. Select the relevant operating system. Use “Other” for the MVSand OS/390 agent.

4. Enter the Domain or select it from the “Master”

5. Enter the Time Zone, Description (optional).

6. In the Options area, select the Extended Agent. The screen isdefaulted with Autolink checked.

7. Enter the access method, MVSOPC, MVSCA7, or MVSJES.Enter the host name. Click on OK then FILE > SAVE. Close thewindow.

See Method Options Files below for information about configuringthe access methods.

Command Line ExampleWorkstation definitions can also be entered at the command lineusing the composer program. The workstation definition shown inthe previous example would be entered as follows:



cpuname mvs2node hal.acme.comos othertcpaddr 5000description "MVS extended agent #2"for Workload Scheduler

host ux4access mvsjes

end

For information about using composer, refer to the Tivoli WorkloadScheduler User’s Guide.

Method Options FilesTo select options for a method, create an options file having thesame path name as the method, with an ″opts″ extension. Forexample, create the following files on UNIX (assuming TWS’s homedirectory is /usr/lib/maestro):/usr/lib/maestro/methods/mvsca7.opts

/usr/lib/maestro/methods/mvsjes.opts

/usr/lib/maestro/methods/mvsopc.opts

Or create the following files on Windows NT (assuming TWS isinstalled in the path C:\WIN32APP\maestro):C:\WIN32APP\maestro\METHODS\MVSCA7.OPTS

C:\WIN32APP\maestro\METHODS\MVSJES.OPTS

C:\WIN32APP\maestro\METHODS\MVSOPC.OPTS

For mvsca7, mvsjes, and mvsopc the options file entries are:

Options File Entries Description

LJuser=name (Required) Assigns the user name used bythe access method to launch jobs. This mustbe a valid UNIX user who is able toconnect to Workload Scheduler’s MVSgateway on the MVS system and submitjobs.

CFuser=name (Required) Assigns the user name used bythe access method to check filedependencies. It must be the same asLJuser.



2.S

etU

pan

dO

peratio

n

Options File Entries Description

GSuser=name (Optional) Assigns the user name used bythe access method to checknon-TWS-launched jobs on MVS that areused as dependencies. The default is root.

CheckInterval=min (Optional) Defines the polling rate, inminutes, for checking the status of MVSjobs that were launched by the method.Fractional values are accepted; for example,.5 for 30 seconds, or 1.5 for one minuteand 30 seconds. The default is 2.

When checking non-TWS-launched jobs onMVS that are used as dependencies, themethod uses the TWS local option bmcheck status instead of CheckInterval todetermine its polling rate. For informationabout TWS’s local options, see section 2 ofthe Tivoli Workload Scheduler User’sGuide.

BlockTime=min (Optional) Defines the amount of time, inminutes, the method will wait for aresponse to a status check before timingout. This value must be less than the valueof CheckInterval(described above) andTWS’s local option bm check status.Fractional values are accepted; for example,.5 for 30 seconds, or 1.5 for one minuteand 30 seconds. The default is 2.

RetryCount=count (Optional) Defines the number of times astatus check is attempted before TWSwrites a timeout message to a job’s stdlistfile and marks it in the abend state. SeeCheckInterval and BlockTime above formore information. The default is 10.

Any changes made to a method options file do not take effect untilTWS is stopped and restarted.



Using a Method Multiple TimesThe same method can be used for multiple x-agents. Note, however,that if the method name is the same, the x-agents will use the samemethod options file. To permit the use of separate options files,make copies of the method and give each copy a unique name. Usethese names in the x-agent workstation definitions and to createunique options files.

Defining Jobs in MVS and OS/390In MVS and OS/390, jobs that are scheduled with TWS are definedas prescribed for JES, CA7 and OPC.

Defining MVS and OS/390 Jobs in WorkloadScheduler (TWS)

TWS job definitions are required for each MVS and OS/390 job youintend to schedule and launch with TWS. They are defined like otherTWS jobs and include job name, user name, special script nameoptions, and optional recovery options. Both the legacy GUI and theJS Console GUI screens are shown here. Figure 3 shows a MaestroComposer Job Definition Window for a job named IEFBR14.Figures 4 and 5 show the JS Console GUI Job Definition windows.For information about using gcomposer, refer to the Tivoli WorkloadScheduler User’s Guide.



2.S

etU

pan

dO

peratio

n

The fields in the legacy GUI window are described here:

Field Description

Legacy GUI

Workstation: The name of the Extended Agent for MVS on which thejob will run.

Job Name: The name by which the job is scheduled in TWS. Thename can contain up to eight characters starting with aletter.

Logon: The user name used by the access method to launch thisjob. This must be a valid UNIX user who is able toconnect to TWS’s MVS gateway on the MVS system,and submit jobs. If LJuser is specified in the methodoptions file, it overrides this user name.

Description: An optional free-form textual description of the job (upto 40 characters).

Figure 3. Defining an MVS and OS/390 Job (Legacy GUI)

Defining MVS and OS/390 Jobs in Workload Scheduler (TWS)


Field Description

Script File: The identification of the MVS job to be launched ormonitored. For specific information about JES, CA7,OPC, refer to:“Script File Syntax for TWS-ScheduledMVS Jobs” on page 26 and “Syntax for MVS andOS/390 Job Dependencies” on page 28.

Interactive: Not used.

Command: Not used.

Stop ContinueRerun

These buttons determine the action taken if the jobterminates abnormally. Stop Do not continue with thenext job. Continue Continue with the next job. RerunRerun the failed job.

Recovery Job: The TWS name of a recovery job.

RecoveryPrompt:

The text of a recovery prompt.

LoadBalancing:

Not Used. Only appears in the UNIX version.



2.S

etU

pan

dO

peratio

n

Figure 4. Defining an MVS and OS/390 Job [″General″ Option, JS Console] - Screen 1 of 2



The fields in the ″General″ and ″Task″ JS Console GUI screens aredescribed here:

Field Description

JS Console GUI

″GENERAL″ Window

Name: The name by which the job is scheduled inTWS. The name can contain up to eightcharacters starting with a letter.

Workstation: The name of the Extended Agent for MVS onwhich the job will run.

Description: An optional free-form textual description of thejob (up to 40 characters).

Figure 5. Defining an MVS and OS/390 Job [″Task″ Option, JS Console] - Screen 2 of 2



2.S

etU

pan

dO

peratio

n

Field Description

Login: The user name used by the access method tolaunch this job. This must be a valid UNIX userwho is able to connect to TWS’s MVS gatewayon the MVS and OS/390 system, and submitjobs. If LJuser is specified in the methodoptions file, it overrides this user name.

Parameters: The identification of the MVS and OS/390 jobto be launched or monitored. For specificinformation about JES, CA7, OPC, referto:“Script File Syntax for TWS-Scheduled MVSJobs” on page 26 and “Syntax for MVS andOS/390 Job Dependencies” on page 28.

Stop Continue Rerun Recovery Options: These buttons determine theaction taken if the job terminates abnormally.Stop Do not continue with the next job(Default). Continue Continue with the next job.Rerun Rerun the failed job.

Message Optional text user can add to describe the job.

JS Console GUI

″TASK″ Window

Task: The name by which the job is scheduled inTWS. The name can contain up to eightcharacters starting with a letter.

Add Parameter ...: The identification of the MVS and OS/390 jobto be launched or monitored. For specificinformation about JES, CA7, OPC, referto:“Script File Syntax for TWS-Scheduled MVSJobs” on page 26 and “Syntax for MVS andOS/390 Job Dependencies” on page 28.

Procedure to Define an MVS and OS/390 Extended Agent Job(Legacy GUI)



To define an MVS Extended Agent job on the legacy GUI, followthese steps:

1. From the main JS Console window, either from the top toolbar,select the ″New Job Definition″ icon and follow from step 2below, or from the main window right click on TWS7.0 andselect ″New Job Definition″ from the drop down menu.

2. In the Select a Task Type screen, select Extended Agent Task >OK.

Procedure to Define an MVS and OS/390 Extended Agent Job(JS Console GUI)

To create a new job on the JS Console follow these steps:

1. Either select the ″New Job Stream″ icon in the top tool bar orfrom the TWS7.0 navigation bar, click right and from the dropdown menu, select ″New Job Stream″. Note ″Job Stream″ usedto be called ″Scheduler″.

2. From the General screen, enter the job stream name. Select theworkstation.

3. Enter a description (optional), the priority and limit.

4. Enter the time restrictions, resources, and file information.

5. For further details, see the Tivoli Workstation Scheduler (TWS)7.0 User’s Guide.

Command Line ExampleJob definitions can also be entered at the command line using thecomposer program. The job shown in the Job Definition window on“Defining Jobs in MVS and OS/390” on page 19 would be enteredas follows:mvs2#iefbr14

streamlogon mvsjobsdescription "MVS job #iefbr14"scriptname "acorn.mktg.mvsiefbr14 = 0002"

recovery continue after iefbr14recv




2.S

etU

pan

dO

peratio

n

Script File Syntax for TWS-Scheduled MVS JobsFollowing are descriptions of the Script File (command line“scriptname”) syntax for MVS jobs that TWS schedules andlaunches via x-agent workstations defined with the mvsjes (JES2/3jobs), mvsca7 (CA7 jobs), and mvsopc (OPC jobs) methods.

For JES jobs:dataset [<|= condcode]

where:

datasetThe JES job’s data set or partitioned data set name.

condcodeThe condition code that indicates successful job completion.If preceded by <, the condition code must be less than orequal to this value. If preceded by =, the condition codemust be equal to this value. If omitted, “= 0000” is used.Note that there must be a space on both sides of the operator(< or =).

Example:gold.apayable.cntl(apayjob1) = 0004

For CA7 jobs:jobname [SCHID(nnn)] [CC(nnnn) ] [...]

[RO(EQ|LT|GT|GE|LE|NE|#S|IG|NO) ]

[SET(SKP|NTR|NDB) ]

where:

jobnameThe name of the job in CA7.

SCHIDThe schedule id (a number 1-255) to be assigned to the job.

CC The condition code used with RO that indicates successfuljob completion.

RO The relational operator for condition code CC.



SET Sets job options to skip the next scheduled run (SKP),disable normal job triggering (NTR), or bypass databaseloading on completion (NDB).

For complete descriptions of the parameters, refer to your CA-7Commands Guide.

Example:ARCVJOB SCHID(203) CC(0001) RO(EQ) SET(NDB)

For OPC jobs:appl [IA(yymmddhhmm)|IATIME(hhmm) ] [...]

[DEADLINE(yymmddhhmm)|DEADLINETIME(hhmm) ]

[PRIORITY(pri) ]

[CPDEPR(Y|N|P|S) ]

where:

appl The name of the OPC application to be inserted into thecurrent plan.

IA The input arrival date and time in the form: yymmddhhmm .

IATIMEThe input arrival time in the form: hhmm.

DEADLINEThe deadline arrival date and time in the form:yymmddhhmm.

DEADLINETIMEThe deadline arrival date and time in the form: hhmm.

PRIORITYThe priority (1-9) at which to run the application..

CPDEPRThe current plan dependency resolution selection.

Y Add all successor and predecessor dependencies.

N Do not add any dependencies. (The default.)

P Add predecessor dependencies.



2.S

etU

pan

dO

peratio

n

S Add successor dependencies.

For complete descriptions of the parameters, refer to your OPCdocumentation.

Example:PREFABJOB44 IA(9792181000) PRIORITY(5) CPDEPR(Y)

Syntax for MVS and OS/390 Job Dependencies

(Tivoli Workload Scheduler (TWS) version 5.0 and above)Following are descriptions of the Script File (command line“scriptname”) syntax for MVS and OS/390 jobs that were notlaunched by TWS, but are to be monitored for completion. Thecompletion of these MVS and OS/390 jobs can be used as “follows”dependencies for TWS-launched jobs. The non-TWS jobs can beJES, CA7 or OPC.

The basic syntax is:tws-job follows xagent::"mvs-job"

where:

tws-jobThe name of the Workload Scheduler-launched job thatdepends on the completion of the specified MVS job.

xagent The name of the Workload Scheduler x-agent workstationassociated with the scheduler of the MVS job— that is, anx-agent defined with the mvsjes, mvsca7, or mvsopcmethod. Note that the two colons are a required delimiter.

mvs-jobThe identification of the MVS and OS/390 job. Note thatthis string must be enclosed in quotation marks. See thesyntax descriptions below.

When Using gcomposer (Legacy GUI)When using gcomposer to add job dependencies, use theInternetwork field on the Follows Sched/Job panel to identify theMVS job, and then click the <<Addbutton. For example:



Internetwork: jesworkstation::"apayable = 0004"

For JES jobs:"jobname[<|= condcode]"

where:

jobnameThe name of the job in JES.

condcodeThe condition code that indicates successful job completion. Ifpreceded by <, the condition code must be less than or equal tothis value. If preceded by =, the condition code must be equal tothis value. If omitted, “= 0000” is used. Note that there must bea space on both sides of the operator (< or =).

Example:job5 follows jesworkstation::"apayable = 0004"

For CA7 jobs:"jobname [SCHID(nnn) ] [...]"

[DATE(*|*yyddd)} ]

[SPAN( {* }) ]

{scope }

{date }

{(startdate,starttime,scope) }

{(startdate,starttime,enddate,endtime) }

where:

jobnameThe name of the job in CA7.

SCHIDThe schedule id (a number 1-255) of the job.

DATE A specific log date to be searched for the job.

SPAN The span of log records to be searched for the job.



2.S

etU

pan

dO

peratio

n

For complete descriptions of the parameters, refer to your CA-7Commands Guide. For example:joba follows workstation::"arcvjob schid(203) span(12)"

For OPC jobs:"application[IA(yymmddhhmm)|IATIME(hhmm)][...]"

[JOBNAME(jobname) ]

[OPNO(num) ]

where:

applicationThe name of the OPC application in the current plan.

IA The input arrival date and time.

IATIMEThe input arrival time.

JOBNAMEThe MVS job name.

OPNOThe operation number (1-99). If included, the job is consideredcompleted when it reaches this operation number.

For complete descriptions of the parameters, refer to your OPCdocumentation.

For example:joba follows opcworkstation::"PREFABJOB44 IA(9792181000) JOBNAME(PFJ3)"

Note: If OPC goes down and comes back up, the address is incorrectfor the new OPC occurrence. You must restart TSSERVER.

Scheduling MVS and OS/390 JobsMVS and OS/390 jobs are scheduled in the same manner as otherTWS jobs and can include dependencies and other constraints,including Opens Files dependencies. Only the legacy GUI screenversion is shown here.



Figure 6 shows legacy GUI (Schedule) Job Stream Definitionwindow for a schedule named MVSCPU#TSO36JCC in the processof adding job 1EFBR14RTP to the job stream. For information aboutusing the legacy GUI and gcomposer, and Job Stream Definitionusing the JS Console GUI refer to the Tivoli Workload SchedulerUser’s Guide.

Command Line ExampleSchedules can also be entered at the command line using thecomposer program. The schedule shown in the previous example,including dependencies, would be entered as follows:schedule uxmaster#glsked

on monthendat 1600

:apjobux1#arjob

Figure 6. Scheduling MVS Jobs (Legacy GUI)



2.S

etU

pan

dO

peratio

n

mvs2#gljob follows apjob,ux1#arjobopens mvs2#"PROD.LEDGER.FILE"

gls follows mvs2#gljobend




Reference Information

Technical Overview

Operation with JES

Launching JES JobsTo launch and monitor a JES job, Workload Scheduler (TWS) passesthe name of the JCL data set or pds it wants executed to the MVSgateway, which, in turn, submits it to JES. Submissions occur usingdynamically allocated internal readers in JES. The Gateway allocatesan internal reader at the start of each task and then submits the jobto the reader.

When a job is submitted, the job name and JES Job ID are alsoentered in the Tablespace. When an SMF record containing relevantjob scheduling data is passed through the IEFU84 exit, the job andcondition code information are made available to TWS. SinceWorkload Scheduler keeps track of both the job name and JES jobID, it is able to check for the specific job it submitted. (Currently theGateway uses Type 30 SMF records and also subtypes 1,4,5.)

TWS checks submitted jobs periodically to see if they are active. Ifa TWS-submitted job is not active and no information about it isfound through the IEFU84 exit, the job is marked as abend inWorkload Scheduler displays. This situation can occur if a job failsfor security reasons or JCL syntax problems.

3


3.R

eference

Info

rmatio

n

JES Job States

WorkloadScheduler JobState

JES Job State Comments

intro na Workload Scheduler is starting themethod.

wait Queued

wait + na If the job remains in this state, it maybe due to a security violation in MVS.Check the job on the MVS system.

exec Executing Job is executing.

succ Completed Job’s condition code meets thecompletion criteria in the WorkloadScheduler job definition.

abend Completed Job’s condition code does not meet thecompletion criteria in the WorkloadScheduler job definition, or a systemor user abend has occurred. Systemabends codes, in hex, are prefixed with″S″, and user abend codes, in decimal,are prefixed with ″U″. Both types ofcodes are written to the job’s stdlistfile.

extrn na Status unknown. Can occur only whenchecking a job that is used as adependency.

Checking JES JobsTo check a JES job that was not launched by Workload Scheduler(TWS), the name of the job is passed by Workload Scheduler to theGateway. Because Workload Scheduler did not submit the job, theJES Job ID is not available. The Gateway enters the name in theTablespace, and waits for information about the job to appear inSMF records passed through the IEFU84 exit.

Technical Overview


Operation with CA7

Launching CA7 JobsTo launch and monitor a CA7 job, Workload Scheduler passes thejob name, and optionally the CA7 schedID, it wants executed to theMVS Gateway. At the time of the submission request, the Gatewayreceives the CA7 Job Number which is used to track all subsequentactivity for the job. It is important to note that CA7 itself must beauthorized to accept commands from the console in order for thismechanism to work. See the CA7 documentation for a discussion ofthe Modify and Login commands for more information on thisfeature.

CA7 Job States

WorkloadSchedulerJob State

CA7 Job State Comment

intro na Workload Scheduler is starting themethod.

wait Request Queueor Ready Queue

The wait state may also indicate that thejob moved from the Active queue to theRequest queue as the result of an abend.The job remains in the Request queue,with a restart prompt, until the operatoreither restarts or cancels it.

exec Active Queue

succ Completed Job’s condition code meets thecompletion criteria in the WorkloadScheduler job definition.

abend na Job’s condition code does not meet thecompletion criteria in the WorkloadScheduler job definition. Also see notebelow.

extrn na Status unknown. Can occur only whenchecking a job that is used as adependency. Also see note below.

Technical Overview


3.R

eference

Info

rmatio

n

Note: If a job remains in the abend (Maestro 4.5) or extrn(Maestro 5.0 and above), it may be due to a security violationin MVS. Check the job on the MVS system.

Note: The states in the above table refer to those on the legacy GUITWS Extended Agent Workload Scheduler screen. For thenewer GUI Job Scheduling Console states (status) seen on theJSConsole Workload Scheduler screen, refer to page 359 ofthe TWS User’s Guide.

Checking CA7 JobsTo check a CA7 job that was not launched by Workload Scheduler,the name of the job, and optionally the CA7 schedID, is passed byWorkload Scheduler to the Gateway. To see if the job is currentlybeing scheduled or executed by CA7, the Gateway searches thefollowing CA7 queues, in this order: Request Queue, Ready Queue,and Active Queue. If the job is not found, Workload Schedulerrechecks at a rate defined by one of the following:

¶ For the mvsca7, mvsjes, and mvsopc methods, the bm checkstatus value in Workload Scheduler’s Local Options file.

Other CA7 TipsWhen using CA7, CA7USER must also be a valid UNIX id.

When defining CA7 jobs in TWS, SCHID is required.

Operation with OPC

Launching OPC JobsTo launch and monitor an OPC job, Workload Scheduler passes theapplication name, and other optional parameters, it wants executed tothe MVS Gateway. If it exists in the OPC database, the applicationis inserted in the current plan. The input arrival, deadline arrival,priority, and automatic dependency resolution parameters, ifincluded, override any values specified in OPC.

At a rate defined by the CheckInterval value in the method optionsfile, Workload Scheduler checks the status of the occurrence(application) in OPC.

Technical Overview


OPC Application States

Workload Scheduler JobState

OPC Application State

wait pending

wait undecided

exec started

succ complete

abend error

abend deleted

abend N/A

extrn N/A Status unknown. Can occur only when checking a jobthat is used as a dependency. Also see note below.

OPC Occurrence States

Workload Scheduler JobState

OPC Occurrence State

wait pending

wait undecided

wait wait

wait ready

exec started

succ complete

abend interrupted

abend error

abend deleted

abend na

extrn na

Notes:

1. If a job remains in the abend (Maestro 4.5) or extrn (Maestro5.0 and above), it may be due to a security violation in MVS.Check the job on the MVS system.

Technical Overview


3.R

eference

Info

rmatio

n

2. When defining OPC jobs in TWS, either the IA or IATIMEneeds to be used. One or the other is required!

3. The states in the above table refer to those on the legacy GUITWS Extended Agent Workload Scheduler screen. For the newerGUI Job Scheduling Console states (status) as seen on the JSConsole Workload Scheduler screen, refer to page 359 of theTWS User’s Guide.

Checking OPC JobsTo check an OPC job that was not launched by Workload Scheduler,the name of the application, and optionally the operation, is passedto the Gateway. A check is made to see if the occurrence oroperation is in the current plan. If it is not found, WorkloadScheduler rechecks at a rate defined by one of the following:

¶ For the mvsca7, mvsjes, and mvsopc methods, the bm checkstatus value in Workload Scheduler’s Local Options file.

Checking for Files on MVS and OS/390OS/390The existence of a file can be used as a job dependency in WorkloadScheduler (TWS). To check for the existence of a file on MVS andOS/390, Workload Scheduler passes the file name to the Gateway.The file name is allocated with DISP=OLD, and is considered toexist if: 1) the data set exists, 2) it is allocated, and 3) it is not inuse by another task. If the data set does not exist, WorkloadScheduler continues to wait and check for the file at a predeterminedinterval.

Note that Workload Scheduler can only use fully qualified data setnames for non partitioned files. If a Generation Data Group name isto be used, it must be the fully qualified name and not a relativename (e.g. xxxxx.xxxxx(-1) cannot be used).

Timing ConsiderationsWhen checking MVS and OS/390 jobs that were not launched byWorkload Scheduler, certain timing issues are critical to assuring thatany associated job dependencies are correctly resolved. These issuesarise as the result of Workload Schedulers conception of aprocessing day. A full discussion can be found in the Tivoli Workload

Technical Overview


Scheduler User’s Guide. In short, Workload Scheduler regenerates itsproduction schedule each day at a preset time; for example, 6:00 amevery morning. To maintain a working relationship between jobsbeing run under MVS and jobs being run under Workload Scheduler,some synchronization between the two environments is necessary. If,for example, an MVS job is started outside of Workload Scheduler,and completes before the start of Workload Schedulers processingday, it will not be visible to Workload Scheduler and should not beused in a Workload Scheduler job dependency. Workload Schedulermakes no attempt to determine the status of jobs that completedbefore its start of day.

If synchronization is not taken into account, as discussed above,Workload Scheduler may wait indefinitely to resolve a jobdependency. A similar problem can occur as the result of acommunications failure between the MVS and Workload Schedulerenvironments that prevents Workload Scheduler from determiningthe status of an MVS job to satisfy a job dependency.

Diagnostic InformationMVS and OS/390 jobs submitted by Workload Scheduler (TWS) canfail to complete for a number of reasons. The step in the submissionprocess in which a job fails determines how much information isavailable to and provided by Workload Scheduler as follows:

¶ If a job fails before it is actually initiated (usually the result of aJCL or security problem) Workload Scheduler recognizes that itno longer exists, and marks it as abended in Console Manager(Conman) displays. No further information is provided.

¶ If a job fails after being started, Workload Scheduler obtains itscondition code and user abend code, if any, writes them to thejob’s standard list file, and then marks the job as abend inConsole Manager (Conman) displays. Job standard lists can bedisplayed with the Console Manager (Conman).

Technical Overview


3.R

eference

Info

rmatio

n

Gateway MessagesInformative messages are dynamically created by the MVS gatewayprogram. Along with condition-specific information, the messagesinclude:

¶ Module name

¶ Label within the module

¶ Macro name

¶ Reason code (register 0)

¶ Return code (register 15)

The MVS gateway messages are listed below. For module names(module), see below.TSI001E module FAILED, MACRO macro NEAR LABELlabel WITH RETURN CODE = code & REASON CODE =code

TSI002E module FAILED, MACRO macro NEAR LABELlabel WITH ERROR NUMBER = err

TSI003I module ISSUED, MACRO macro NEAR LABELlabel TO OBTAIN SOCKET DESCRIPTOR = desc

TSI004I module ISSUED, MACRO macro NEAR LABELlabel TO OBTAIN HOSTNAME = host

TSI005I module TCPIP ADDRESS = ipaddress

TSI006I module name = name

TSI007I module ISSUED, MACRO macro NEAR LABELlabel FOR num CHARACTER MESSAGE = msg

TSI008S module FAILED AT OFFSET offset

TSI009E module FAILED, MACRO macro NEAR LABELlabel WITH RETURN CODE = code

TSI010S module ABENDED WITH ASSOCIATED REASONCODE code

TSI011I module CONSOLE name ACTIVATED WITHCONSOLE ID id

TSI012I module SUBTASK name COMPLETED WITHCOMPLETION CODE code

TSI013I module CALL TO "name" NEAR LABEL labelCOMPLETED WITH COMPLETION CODE code

TSI014S module INVALID DATA SPACE FOUND NEARLABEL label

Gateway Messages


TSI015E module DATASET "dset" DDNAME "dd"FAILED TO OPEN NEAR LABEL label

TSI016I module SUBMITTED JOB "job" WITH JESIDENTIFICATION "id"

TSI017I module PEERADDRESS = ipaddress

TSI018E module INVALID TERMINATOR term

TSI019E module NEAR LABEL label INVALID VALUEFOUND name = value

TSI020E module NEAR LABEL label FAILED TO FINDACTIVE SMF IEFU84 EXIT

TSI021E module FAILED, MACRO macro NEAR LABELlabel

The module names are:

Module Name Description

TSITCPCF Check file request handler

TSITCPCJ Check job request handler

TSITCPL7 Launch CA7 job request handler

TSITCPEJ Enumerate job request handler

TSITCPFJ Free job request handler

TSITCPKJ Kill job request handler

TSITCPLJ Launch job request handler

TSITCPQJ Query job request handler

TSITCPQ7 Query CA7 job request handler

TSITCPQS Query subsystem request handler

TSITCPWS Wait for specified amount of time

TSITCP00 Main processing routine

TSITCP01 Server test vehicle

TSITCP02 Main dataspace construction routine

TSITCP05 Establish ESTAE routine to issue failure message

TSITCP07 Find dataset name associated with open ACB/DCB

TSITCP08 Find dataset name associated with DDNAME

TSITCP10 Initialize and examine variables

TSITCP15 Locate and initialize control blocks

Gateway Messages


3.R

eference

Info

rmatio

n

Module Name Description

TSITCP20 Locate and initialize control blocks

TSITCP21 Client test vehicle



TSITCP25 Concurrent server

TSITCP26 Concurrent server Interlink TCPIP provider

TSITCP27 Concurrent server for Openconnect TCPIP stack

TSITCP30 Child server task

TSITCP31 Child server task for Interlink TCPIP stack

TSITCP32 Child server task

TSITCP84 SMF record exit for SMFEWTM

TSITCP90 Issue command and wait for response

TSITCP91 Issues TERROR to format messages and issues WTOS

TSITCP92 Find substring within string

TSITCP93 Issue CA7 command and wait for response

TSITCP94 STIMER exit to post ECB past in parm

TSITCP95 Calls IKJEFF02 to extract buffer using TSITCP99

TSITCP96 ESTAE routine to issue failure message

TSITCP97 Calls IKJEFF19 (DAIRFAIL/VSAMFAIL) to issue message

TSITCP98 Calls IKJEFF02 to issue message from TSITCP99

TSITCP99 Message table

TSITSTED String encryption/decryption test routine

For descriptions of return codes (rt) and reason codes (re) refer tothe appropriate IBM documentation for your system.

To assist in troubleshooting, be sure to obtain a system log, and thesystem print log for the TSDSPACE and TSSERVER job streams.These will help in determining the context in which a message wasissued.

Gateway Messages


Index

Aaccess method

types 13, 15using multiple times 19

application states for OPC 37

Bbm check status 36, 38

CCA7 jobs 26CA7 operation overview 35CA7NAME 8CA7USER 8CFuser 17CheckInterval 18console security 7CPU Name 14

DDEBUG 8dependency on MVS jobs 28diagnostic information 39

Eerror messages 42

Ffeatures 1

Ggateway messages 42

HHost CPU 13, 15

IIEFU84 exit 6, 7installation 10INTERLINKSUBSYSTEM 8

JJCL to unload the tape 4JCL TSPACE 7JES jobs 26JES operation overview 33, 34Job Name 20, 23, 24job states for CA7 35job states for JES 34job states for OPC 37


Ind

ex

LLJuser 17Logon 20, 24

MMAXWAIT 8MCSSTORAGE 8messages 42MVS job dependencies 28MVS jobs

scheduling 31mvsca7 13, 15mvsjes 13, 15mvsopc 13, 15

NNode 12, 14

Ooccurrence states for OPC 37OPC jobs 27OPC operation overview 36OPCMSGCLASS 9OPCSUBSYSTEM 9Operating System 12, 15OPERCMDS 7

PPEERADDRESS 9PORT 9PUTLINE 9

QQLIMIT 9

RRecovery Job 21, 24Recovery Prompt 21

Sscheduling 31Script File 21, 28security 6start up 7SUBSYS 9SVCDUMP 9SYSTSIN variables 8

TTCP Address 12, 15TCP/IP version 2TCPIP stack 9TCPIPSTACK 9TCPNAME 9technical overview 33TERMINATOR 9TSPACE 7

Uunloading files 4


WWTP 10


Ind

ex

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0642-00