Troubleshooting
Problem
Cause
Resolving The Problem
1. Logon as the user that jobs have issues launching scripts
2. Execute the following:
env > /tmp/userenv
3. While logged on as the same user execute conman
4. From within conman execute the following command specifying for logon the "username" of the user having problems executing scripts:
sbd env;logon=username
5. Compare the result of the env command that was created in step 2 to the job stdlist output from step 4. Whatever environment variables that exist in the output of step 2 must be available to TWS via .jobmanrc for scripts to launch.
NOTE: The .jobmanrc must exist in the home directory of the user for which the job will launch.
The .jobmanrc must also have execute permission for the owner and must not have any terminal settings or stanzas that require a reply. The following is a sample .jobmanrc:
***************************************************************
#!/bin/ksh
## Maestro user .jobmanrc
PATH=$HOME:$HOME/bin:/bin:/usr/bin:/usr/sbin:/usr/ucb:/usr/bin/X11:/usr/local/bin:$HOME/bin:.
## Set up the shell environment
## Here are some common aliases, the following is optional
## Just an example of what can be done
alias ls='ls -F'
alias sj='conman sj'
alias sc='conman sc'
alias ss='conman ss'
alias v='conman status'
alias cds='cd $STDLIST'
alias ll='ls -l'
# Any application specific paths or variables like for
# Oracle may be included here also
# The following line is required and must be the last line of the
# .jobmanrc
/bin/sh -c "$UNISON_JCL"
Historical Number
1018783
Product Synonym
Maestro;TWS;IWS;TWA
Was this topic helpful?
Document Information
Modified date:
19 August 2020
UID
swg21155953