An batch job is submitted via TESTEXEC using a SUBJOB macro in a Global Process.
It looks like the proc executed successfully
RMMO0120 EXECUTING PROCESS(MAILTEST) FOR <user1>
But no job actually ran.
The log shows
S RDR,UNIT=,LABEL=,VOL=,DCB=,BLKSIZE=,DISP=SHR,DSNAME=hlq.JCLLIB(TEST1)
ACF01004 LOGONID RDR NOT FOUND
IEE296I RDR FAILED BY SECURITY INTERFACE. RC=00000004 RSN=00000000 SAFRC=00000008
The RDR STC is started by Netmaster. The ACF01004 message indicates that no logonid exists.
By default, the SYS1.PROCLIB has a member called RDR that executes a program called IEBEDIT:
//RDR PROC CLASS=A
//IEFPROC EXEC PGM=IEBEDIT
//SYSPRINT DD SYSOUT=A
//SYSUT1 DD DDNAME=IEFRDER
//SYSUT2 DD SYSOUT=(&CLASS,INTRDR),DCB=BLKSIZE=80
//SYSIN DD DUMMY
//IEFRDER DD UNIT=TAPE,LABEL=(,NL),VOL=SER=JES2IN,DISP=OLD,
// DCB=(RECFM=F,BLKSIZE=80,LRECL=80)
This is what Netmaster is using for the SUBJOB process.
The problem is that either no logonid for RDR exists, or the procname is different.
Please do the following:
1. Check the SYS1.PROCLIB and search for any member that contains the IEBEDIT program by using the command
SRCHFOR IEBEDIT
in the command line above the member list.
2. If RDR is the correct name, the logonid is missing.
In ACF2 this can be added using the command
ACF
INSERT RDR STC name(reader logonid)
END
3. If the proc has a different name, the following change is required:
In the NetMaster region, go to /PARMS and update the $RM AUTOFILES parameter group with
the membername being used.
On the second screen of the parameter group it shows
+- AUTOFILES - Automation Files Specification -------------------------------+
| |
| Internal Reader Start: |
| RDR,UNIT=,LABEL=,VOL=,DCB=,BLKSIZE=,DISP=SHR |
| |
| Default JCL Library Name: |
| hlq.JCLLIB |
| |
+----------------------------------------------------------------------------+
The internal reader must be changed to match your environment.
If your proc is called RDRSYSA, AUTOFILES must be updated to contain
RDRSYSA,UNIT=,LABEL=,VOL=,DCB=,BLKSIZE=,DISP=SHR
After making the change, try re-running the failing process and see if it works.
- If it works, you're done.
- If the problem persists(i.e. ACF01004 LOGONID RDRSYSA NOT FOUND), the logonid is missing.
Issue the command as in Step 2 but using your procname instead of RDR.