|
View previous topic :: View next topic
|
| Author |
Message |
surya anem
New User
Joined: 20 Dec 2007
Posts: 54
Location: Hyderabad
|
|
|
|
Hi,
I am trying to call a Batch module from CICS module.
The call is failing with
RESPONSE CODE: 12
REASON CODE: 414
DPL RESPONSE: 0
I searched the manual and found that IRP_ABORT_RECEIVED is the problem.
But can someone help me solve this problem
Thanks,
Surya |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
| I am trying to call a Batch module from CICS module. |
Why would you try to call a batch program from CICS? What guarantee have you that the batch region will be executing at the time you issue the call?
The EXCI interface is provided for doing the opposite of what you say you are trying to do - it provides an interface with CICS applications from Batch.
If you need the functionality of the batch program in a CICS application you should CALL or EXEC CICS LINK to it and have the library with the module avaiolable in the DFHRPL concatenation.
Garry. |
|
| Back to top |
|
|
surya anem
New User
Joined: 20 Dec 2007
Posts: 54
Location: Hyderabad
|
|
|
|
| I am extremely sorry. i am trying to call a Online module from Batch module. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
From the manual:
| Quote: |
414 IRP_ABORT_RECEIVED
Explanation: Whilst processing a DPL request, an error occurred in the CICS server region, resulting in an abort FMH7 flow being returned to the external CICS interface.
System Action: A message is returned to the client application program. This is the message that would have been issued to the terminal if the server program had been initiated from a terminal. A pointer to the message is returned to the client application program in the message pointer field of the EXCI return area. See the description of the EXCI return areas for the exact definition of the message format. The pipe is put into a "must close" state.
User Response: Use the message to determine the cause of the error. A typical example is where the server transaction cannot be attached, either because is disabled, or it has not been defined, or because of a security failure. Correct the problem, close and reopen the pipe, and reissue the DPL request. |
So what does the returned message say? I would think looking at it would be the FIRST step towards debugging the problem. |
|
| Back to top |
|
|
surya anem
New User
Joined: 20 Dec 2007
Posts: 54
Location: Hyderabad
|
|
|
|
It just gave a message that response code is 414.
No other information.
we are actually running this program in the System Testing environment.
So, we dont have the facility to change the code now to find out the actual error message.  |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| The message is returned to the batch program. If you cannot find out what that message is, then you'll have to get your site support group to help as we certainly won't be able to discern the contents of the message. |
|
| Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
Tru to look for additional messages in the CICS task outputs (CEEMSG, MSGUSR etc.)
O. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
Contact your CICS systems support group and make sure the
target CICS region is setup properly to handle an EXCI request.
you might also want to consider Use [URL] BBCode for External Links |
|
| Back to top |
|
|
|
|
