I am getting a user abend when I am trying to call DFHXCIS module from my module.
I am passing the below values in the respective order while calling DFHXCIS in order to initialize the user i.e. my Module- F9B750:-
1. Version-1=1
2. EXCI-RETURN-CODE=LOW-VALUES
3. EXCI-USER-TOKEN=0
4. INIT-USER=1
5. EXCI-USER-NAME=F9B750 (My module name)
But it is giving the below error message:-
CEE3250C The system or user abend U401 R=NULL was issued.
Since the module "DFHXCIS" is like a black box for me, so I am not able to debug it.
Please help me out as we are getting this issue in LIVE environment and the job is failing everyday.
You should assume there is no problem with this module, and you dont have to debug it. Its your program that needs debugging.
If you feel DFHXCIS is a black box: you are right, there is no need to know the internals of this module, just know how to use it.
Keep It Simple - use EXEC CICS LINK !
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
There's a reason for the EXCI interface. Peter, in your comment
Quote:
If you want to call a CICS-program from batch, why dont you use the simpler way, that always works: EXEC CICS LINK !
if the LPAR has 100 active CICS regions running (production, QA, and test) -- exactly what in your recommendation provides the information to the batch program about which of those 100 CICS regions to connect to? And have you ever actually TRIED to do this?
That is why the EXCI interface documentation carefully lays out the steps required; get one of the CALLs out of sequence and you'll have problems.
Timu, have you noticed in the documentation that 401 indicates INVALID_CALL_TYPE in all the call sequences? Perhaps that might indicate that you've got something coded wrong in your CALL? Are you using COBOL, C, assembler, or something else for your program?
Robert,
maybe I simplified a bit, but in the EXEC command you just specify the APPLID() of one of those CICS regions where you want to run the linked to program.
To me, its simpler to code one EXEC command instead of six calls in your batch program.
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
I recently had a choice to assist one customer with a CICS <---> Batch Interface, using ECI or EXCI.
I came to the conclusion, due to low-usage, EXCI would be a wiser choice instead of ECI, which is normally chosen for high-usage. And yes, the only requirement of an EXCI was to pass the APPLID as one of the DPL keywords, but in addition, using a user-defined transid (program-id DFHMIRS), based upon a CPMI definition, because the server-program needed a 512-Byte TWA, as it interfaced with DFHEMTA.
So, it's up to site management, after conversing with the technicians and reviewing the potential growth or static growth of the Interface, that ECI or EXCI would be the right fit.
Bill,
you are confusing me a bit.
This post is an EXCI issue, Call and/or EXEC interface, which is the batch interface to CICS.
ECI is a non-batch interface.
Correct me if I´m wrong.
Deepashu,
if you, after your investigation and debugging, still think there is an error in DFHXCIS, you should contact IBM support.
They will for sure tell you if its an error in their product, or a user error.
