Batch job reflects 8 active TCBs, and the TCB for Co:Z is in a SVC 1 (WAIT) state. The CoZAgent has terminated, but Co:Z Launcher is waiting for something. Can you give me some ideas what may be causing the job to WAIT for something that seems to never occur? I am requesting dump of the job so that I can provide additional detail.
cozagent[N]: version: 1.1.3 2014-11-19
fromdsn(DD:STDIN)[N]: 5 records/400 bytes read; 204 bytes written in 0 millisec
fromdsn(DD:INPUT)[N]: 263 records/16565 bytes read; 16828 bytes written in 0 mi
todsn(DD:OUTPUT)[E]: error: no input data available
todsn(DD:STDERR)[N]: 281 bytes read; 7 records/274 bytes written in 0.210 secon
todsn(DD:STDOUT)[N]: 0 bytes read; 0 records/0 bytes written in 0.209 seconds (
cozagent[E]: Target Program(16682) ended with RC=103
CoZLauncher[E]: CoZAgent process (6529) ended with RC=103
CoZLauncher[E]: m92229@p1edw1c1.vci.att.com target command '/bin/ksh' ended wit
CoZAgent: m92229@blph189 target program '/bin/ksh' PID: 16682
CoZAgent: completed with RC=103
Version: BCPG v1.51
gpg: armor header:
gpg: public key is 46B3DDCB
gpg: encrypted with RSA key, ID 46B3DDCB
gpg: decryption failed: No secret key
todsn-client(16748)[E]: todsn(DD:OUTPUT): error: no input data available, rc=10
todsn-client(16748)[E]: server exit_code=103
Batch z/OS job hangs near termination
Re: Batch z/OS job hangs near termination
The last branch was from A(COZLNCH) + 00016C3C
Re: Batch z/OS job hangs near termination
Good job log:
CoZLauncherŽT: <- agentStdoutThread()
CoZLauncherŽD: Killing child process saf-ssh
CoZLauncherŽD: kill() failed for child proce
(errno2=0x0D10013A)
CoZLauncherŽT: <- cleanup()
CoZLauncherŽI: CoZLauncher ended with RC=0
CoZLauncherŽT: <- run()
CoZLauncherŽT: -> ~CoZLauncher()
CoZLauncherŽT: <- ~CoZLauncher()
Hung job log (after cancelling):
CoZLauncher[T]: <- handleAgentCompletion()
CoZLauncher[D]: agentStdoutThread completed
CoZLauncher[T]: <- agentStdoutThread()
So it looks to be in the "CoZLauncherŽD: Killing child process saf-ssh-agent (7813) with signal" area of logic.
Would having / (root) as the home directory, and probably not having write access to it be the issue?
CoZLauncherŽT: <- agentStdoutThread()
CoZLauncherŽD: Killing child process saf-ssh
CoZLauncherŽD: kill() failed for child proce
(errno2=0x0D10013A)
CoZLauncherŽT: <- cleanup()
CoZLauncherŽI: CoZLauncher ended with RC=0
CoZLauncherŽT: <- run()
CoZLauncherŽT: -> ~CoZLauncher()
CoZLauncherŽT: <- ~CoZLauncher()
Hung job log (after cancelling):
CoZLauncher[T]: <- handleAgentCompletion()
CoZLauncher[D]: agentStdoutThread completed
CoZLauncher[T]: <- agentStdoutThread()
So it looks to be in the "CoZLauncherŽD: Killing child process saf-ssh-agent (7813) with signal" area of logic.
Would having / (root) as the home directory, and probably not having write access to it be the issue?
Re: Batch z/OS job hangs near termination
First, verify that you are not use the "default OMVS segment". This will not work with Co:Z Launcher since it will not be able to terminate its own processes.
If that is not the problem, please run this again and get a trace.
For the trace, there are a couple of changes to make:
1) enable Co:Z Launcher logging:
//STEP1 EXEC PROC=COZPROC,
// ARGS='-LT,t myuser@myhost.myco.com'
2) enable ssh client and z/OS Co:Z Server component tracing:
//COZCFG DD *
ssh-options=-vvv
server-env-COZ_LOG=T,t
If that is not the problem, please run this again and get a trace.
For the trace, there are a couple of changes to make:
1) enable Co:Z Launcher logging:
//STEP1 EXEC PROC=COZPROC,
// ARGS='-LT,t myuser@myhost.myco.com'
2) enable ssh client and z/OS Co:Z Server component tracing:
//COZCFG DD *
ssh-options=-vvv
server-env-COZ_LOG=T,t