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
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,
Code:
HQX7760 ----------------- SDSF PRIMARY OPTION MENU NOT AUTHORIZED FOR CMD
COMMAND INPUT ===> /$AJ(JOBNAME) SCROLL ===> PAGE
DA Active users
I Input queue
O Output queue
H Held output queue
ST Status of jobs
SE Scheduling environments
END Exit SDSF
"NOT AUTHORIZED FOR CMD"
Looks like somehow our site has restricted people from issuing JES commands in batch. I have access to issue this command in interactive mode from SDSF, but not with a batch job.
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
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
Could you please let me know if this would help in diagnosing the problem?
by showing that for the job class you are using You are not allowed to issue commands
but really there is nothing to diagnose...
You have just to realize that, if You have the need to do, You should contact Your support who will be glad to provide You the proper authorizations to use a job class where You are allowed to issue commands
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
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.
Joined: 27 Oct 2009 Posts: 2469 Location: Netherlands, Amstelveen
$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
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.
Agreed .... I was going to go into a long discourse here about SDSF and RACF before remembering that SDSF uses the console interface to communicate with the system not the intrdr interface .
Vasanth could you issue a $DINTRDR command and see what they have defined
