Solving TWS Windows Job Run Issues

Transcription

1 Solving TWS Windows Job Run Issues Michael T. Olivier July 16, IBM Corporation

2 2 Overview TWS Concepts Unique to Windows Jobs Jobs That Don't Work (FAIL and ABEND) Jobs That Misbehave Stuck in EXEC Debugging

3 3 TWS Windows Job Concepts TWS Windows User Object Interactive Flag jobmanrc / djobmanrc

4 4 TWS Windows User Object TWS requires a User object to be defined for every user that runs a TWS job. This is different from how TWS for UNIX works. The User object is built into the Symphony file and must be distributed from the MDM before it can be used.

5 5 Interactive Job Option Allows job access to the Desktop. A job must run without needing user input or this option is required. (Script that prompts, pop-up that must be clicked, etc) The Interactive job option can be specified in the job definition or as a parameter when submitting the job.

6 6 Jobmanrc / Djobmanrc Windows jobs do NOT inherit the user's Windows environment*. The TWS job environment is NOT the same as the Windows login environment. Define the environment in which the TWS jobs are launched.

7 7 Jobmanrc / Djobmanrc - notes djobmanrc should almost always be used instead of jobmanrc. jobmanrc is sometimes replaced by FixPack. Dynamic agents will use djobmanrc by default, if present. (Controlled through tasklauncher.bat)

8 8 Windows Jobs that FAIL User Problem Undefined TWS User object Bad credentials (user non-existent, password incorrect, etc) Windows User Rights missing Script does not exist or inaccessible Interactive flag set, without a desktop login Test these with a simple command (dir)

9 9 Windows Jobs that ABEND (only in TWS) Environment

10 10 Localopts (jm load user profile=on) When enabled, Tivoli Workload Scheduler loads the user profile and the user environment variables for each job run by the agent. Roaming profiles are not supported. Introduced with 8.6 FP02 / FP4

11 11 Matching the Environment Run 'set' command from Windows login session and from TWS job as same user Compare the two files Add missing/different variables to djobmanrc

12 12 Matching the Environment Running set from Windows login session

13 13 Matching the Environment Running set from TWS Example: conman sbd set > c:\temp\twsset.txt ;logon=m86;alias=twsset sort twsset.txt > stwsset.txt

14 14 Matching the Environment Compare the differences

15 15 Matching the Environment Defining missing variables in OFF echo Invoking %USERNAME% DJOBMANRC.CMD V.1 set USERPROFILE=%USERPROFILE% ::Setup User Environment Phase SET CommonProgramFiles(x86)=C:\Program Files (x86)\common Files SET CommonProgramFiles=C:\Program Files\Common Files SET CommonProgramW6432=C:\Program Files\Common Files SET=%PATH%;C:\TEMP ::Launch Operation Phase %ARGS% ::Post Operations Phase :out

16 16 But What If... If using mapped drives, try using UNC format instead. \\machinea\dir\script.exe E:\script.exe Application may REQUIRE active login session. Try running the TWS job with that user logged into Windows desktop.

17 17 Windows Jobs that get stuck in EXEC Application requires the desktop and/or is a GUI Example: Notepad Pop-ups VBS script using default wscript engine Interactive flag Script does not have an exit

18 18 Live Demos

19 19 Q&A