Release a HELD job using JES command in batch.

vasanthz · Posted: Thu May 05, 2011 5:43 pm

Hello,
I am trying to release a HELD job using JES command in batch.

When I issue the release command on the console the command /$AJ(JOBNAME) works releasing the job
But when I try the same command on batch, it does not work with no error messages on the JCL,
Attempt 1: Not working

gcicchet · Posted: Fri May 06, 2011 6:01 am

Hi,

this works for me

vasanthz · Posted: Fri May 06, 2011 11:33 am

Hello Gerry,

Many thanks for the job, I tried it out and the job completed with RC=00.
But the job did not get released. I got the below message on joblog,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Issue a $djobclass(%),long command where % is equal to the jobclass in which the batch job will run and if in the output you see the parameter command(ignore) your sysprogs have disallowed the command for this jobclass

vasanthz · Posted: Fri May 06, 2011 2:30 pm

Hello Nevil,

The response was,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

With command=display the command should work fine(you are authorised to issue command in batch) having read you previous post again it looks like you are using a different profile when you invoke sdsf in batch.Try the following

// VALID JOB CARD
/*$VS,'$aj(jobname)'
//S1 EXEC PGM=IEFBR14

enrico-sorichetti · Posted: Fri May 06, 2011 2:41 pm

vasanthz · Posted: Fri May 06, 2011 2:47 pm

Hello Nevil, Thanks for the swift response,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Can you create a new member with ISPF edit and just insert one line
/*$VS,'$aj(jobname)'

and then submit the member . Depending on how TSO is customised this may or may not work

vasanthz · Posted: Fri May 06, 2011 3:01 pm

Still no joy ):

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Last attempt. Go into sdsf in ispf and issue the command WHO
This will show you various bits of information including GRPINDEX=,GRPNAME=
Then submit your batch job and issie the WHO command in SDSF batch. If a different GRPINDEX and GRPNAME are shown, then in all likelihood your sysprogs have stopped you issueing commands using SDSF batch and we will have to find another route

vasanthz · Posted: Fri May 06, 2011 3:38 pm

Hello Nevil,
Below are the results of the new attempt,

Interactive mode: who command

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Ok the following assumes that your sysprogs have used the default values for the GRPNAMEs that they have used(there is a good chance they have done this as they have used the default grpnames) . When you go into SDSF from ISPF you are assigned a group ISFSPROG this is the default name of the sysprogs group and by default you are allowed to issue commands. When you go into sdsf using batch you are assigned group ISFUSER (the lowest of the low) and by default commands are not allowed. So I do not think there is a way to issue the command using SDSF batch.
However from your jes command we can see that class S has the setting

COMMAND=DISPLAY this means that jes should display the command and then execute it . So theoretically you are authorised to issue the command. All we have to do now is work out why jes is not executing the command, or work out why the command is not being passed to jes. Let me think about this I will try and get back to you.

PeterHolland · Posted: Fri May 06, 2011 4:02 pm

$AJ

Authority Required
This command requires job authority. The description of the $T RDRnn command
explains how to ensure the proper MVS system command group authority is
assigned.
This command requires update security access authority. For a description of
assigning command input authority, see OS/390 JES2 Initialization and Tuning Guide

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

vasanthz · Posted: Fri May 06, 2011 5:52 pm

Nevil,
I really appreciate your thoughts and efforts into this,
Here is the response to $DINTRDR in interactive mode,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

I went back to your original post and read it again. you posted this

vasanthz · Posted: Mon May 16, 2011 11:30 am

Hello,
Apologies for the delayed response, I have'nt been keeping good health lately

There were no IEFC166D messages after IEFC165I.
Also there were no logs of a request to respond for yes or no.

Regards,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Hope you are feeling better. Yet another question, is the job you are trying to release the job you are submitting ?

vasanthz · Posted: Mon May 16, 2011 4:08 pm

Thank you, im recovering well,

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Is the job name unique ? if not instead of releasing the job name release the job number eg $aj1234. If the jobname is not unique jes will not release the job

vasanthz · Posted: Mon May 16, 2011 4:37 pm

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

I ran some tests on a z/OS 1.11 and z/OS 1.12 system. If I disable the ability to issue commands in jes the batch job runs correctly but I get no IEFC165I message. If I enable the ability to issue commands in Jes but remove my RACF authorisation btach job runs ok I get message IEFC165I followed by the command I wish to execute and then a RACF error message. If I then give myself the correct Racf authorisation , I get message IEFC165I followed by the command I wish to execute and the batch job works correctly. According to the manuals if you receive IEFC165I followed by the command unless there is a request for a reply from the operator the command will be executed.
As you are seeing
[quote]05.47.11 JOB05016 IEFC165I // $AJ(JOBNAME) 630
05.47.11 JOB05016 $AJ(JOBNAME)

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

sorry for the incorrect formatting of the previous post

vasanthz · Posted: Tue May 17, 2011 3:53 pm

Hello,

Below is the output of the job, there were no HASP messages before the HASP373 message,