RACF help needed.

[Balr14]

I have an Assembler language mainline program that calls other programs. I didn't write it or link it, but now I need to change it. Before changing it, I ran a test and it ran fine. Then I ran an Assembly and bind to ensure the version of the source code and bind JCL were the same as what was running. Everything matched perfect; source, load image, bind map, etc. The problem is when I execute my version for the same library as the old version, I get this:

10.37.10 JOB00991 +TBVSAM - ABOUT TO LOAD USER PGM
10.37.10 JOB00991 CSV003I REQUESTED MODULE READ/TRA NOT FOUND
10.37.10 JOB00991 CSV028I ABEND806-04 JOBNAME=JOHNTBS1 STEPNAME=STEP01
10.37.10 JOB00991 ICH408I USER(JOHN0 ) GROUP(DEVIDS ) NAME(JOHN XXXXXXXX ) 863
863 IDIXDCAP CL(PROGRAM )
863 INSUFFICIENT ACCESS AUTHORITY
863 FROM IDI* (G)
863 ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )
10.37.10 JOB00991 CSV025I PROGRAM CONTROLLED MODULE IDIXDCAP NOT ACCESSED, USER UNAUTHORIZED

Fortunately, I saved the old version. When I put it back in to the library it runs fine again. I'm not understanding how the same program in hte same load library can fail with RACF errors just because I assembled it. But, I don't know RACF real well.

[Bill Dennis]

You have a STEPLIB that is not defined to RACF in a Program-Controlled environment. Your concatenation turns "dirty" and you can't fetch needed modules.

[Balr14]

I didn't change the STEPLIB DD entries. I just swapped my version of the calling program with an existing one, in the same library.

[Robert Sample]

Is the program authorized? Did you assemble the replacement program authorized?

[Balr14]

No. I figured that was the issue, but it's not something I've had to deal with in many years... don't remember how.

[enrico-sorichetti]

the manual tells

CSV003I REQUESTED MODULE mod NOT FOUND

where mod should be, as per message text, the name of a load module
but the starting post reports

CSV003I REQUESTED MODULE READ/TRA NOT FOUND

where does READ/TRA come from... just curious!
( i might be missing something anyway )

[Balr14]

That is the exact message log content, nothing changed or omitted.

[enrico-sorichetti]

from a manual

Fault Analyzer requires a dump capture exit, IDIXDCAP

does the reference hint something to You ?
why not work a bit with Your support ?

[steve-myers]

This smells like a shell program that loads a program from some sort of parm. The original caller is specifying the program as READ/TRA, where the / is intended as some sort of separator between the program name (READ) and some sort of parameter data (TRA...). If my nose has it right, the real problem could be the program name must be 8 bytes.

The other issue is this IDIXDCAP program. Just out of curiosity I fed it into Google; one of the results was this headline: Installing the MVS change options/suppress dump exit IDIXDCAP. It seems to have something to do with the IBM Fault analyzer product.

[enrico-sorichetti]

revisiting the whole topic
seems to me that You have three issues...
1) - manual reading ( not enough of it )
2) -

10.37.10 JOB00991 CSV003I REQUESTED MODULE READ/TRA NOT FOUND
10.37.10 JOB00991 CSV028I ABEND806-04 JOBNAME=JOHNTBS1 STEPNAME=STEP01

the message sequence is clear You are trying to load something that is not there
done the searching on Your behalf and posting the relevant snippet

806
04
The system could not find the module, whose entry point is the value of the EP or EPLOC operand, in the indicated library (private library, job library, or link library). This situation can occur when LSEARCH=YES is specified on the macro and the limited library search fails to locate the module. For an alias name, ensure that the entry point attributes match that of the load module which was previously loaded (that is, authorization, RMODE, entry point displacement).

Application Programmer Response: If the reason code is X'04', this is probably a user error. Make sure that the requesting program was not incorrectly modified. Make sure that the source library was indicated correctly and that the indicated library does contain the requested program. For an alias name, make sure the alias attributes match the attributes of the load module which was already loaded; check the library authorization, RMODE, and alias entry point displacement). Also, check that there are no duplicate aliases or related primary module names in the library concatenation. MVS expects that all module names, and aliases, are unique across every library. Correct the error, and run the job step again.

if You are working in a zOS-MVS environment You might have some kind of
storage/addressing issues and trying to load garbage instead of a proper module
if working in a zOS-USS environment ... well, good luck
3) - an installation issue with the authorization to IDIXDCAP module

for 1) and 2) You have to work it out Yourself
for 3) work with Your support