| View previous topic :: View next topic |
| Author |
Message |
djf
Beginner
Joined: 06 Feb 2007
Posts: 68
Topics: 27
|
 Posted: Fri Feb 23, 2007 10:15 am Post subject: CICS quick disconnect |
 |
|
Hello,
I am getting CICS transaction dumps and am fairly certain they are caused by users doing hard disconnects from the region. Is'nt there a SIT parm or something in the VTAM LU definitions that tells him to just let it go and not abend? |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Fri Feb 23, 2007 10:29 am Post subject: |
|
|
Are you abending with abend code ATNI ? If so you need to check for TERMERR on Disconnect Command.
| Code: |
TERMERR
occurs only for an ISSUE DISCONNECT for LUTYPE4 logical units.
It occurs for a terminal-related error, such as a session failure.
This condition applies to VTAM-connected terminals only. Because of
the asynchronous nature of this condition, the application program
should check, using SEND CONFIRM or SYNCPOINT, to make sure any errors
still outstanding have been resolved before it relinquishes control.
If you wish to handle this condition, you must first issue a FREE
command to free the session. If you do not do this, an INVREQ
condition occurs, plus an ATCV abend if you do not handle this
condition.
A CANCEL TASK request by a user node error program (NEP) may cause
this condition if the task has an outstanding terminal control request
active when the node abnormal condition program handles the session
error.
Default action: terminate the task abnormally with abend code ATNI.
|
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
djf
Beginner
Joined: 06 Feb 2007
Posts: 68
Topics: 27
|
| Posted: Fri Feb 23, 2007 10:38 am Post subject: |
|
|
Nope.
We are using an OEM package called TRMS for report archiving/routing/review.
| Code: |
Here is the snapshot:
+DFHAP0001 CICS390A An abend (code 0C1/AKEA) has occurred at offset
X'000014B0' in module VCSICI32.
+DFHME0116 CICS390A
(Module:DFHMEME) CICS symptom string for message DFHAP0001 is
PIDS/5655M1500 LVLS/640 MS/DFHAP0001 RIDS/DFHSRP PTFS/HCI6400
AB/S00C1 AB/UAKEA RIDS/VCSICI32 ADRS/000014B0
+DFHDU0201 CICS390A ABOUT TO TAKE SDUMP. DUMPCODE: AP0001 , DUMPID:
1/0057
IEA794I SVC DUMP HAS CAPTURED:
DUMPID=050 REQUESTED BY JOB (CTS31A )
DUMP TITLE=CICS DUMP: SYSTEM=CICS390A CODE=AP0001 ID=1/0057
|
There might be a parm in the software, but I seemed to remember from years ago that there some DFHZNEP parm or VTAM quick disconnect LU type parm that would do a graceful exit. |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Fri Feb 23, 2007 11:20 am Post subject: |
|
|
djf,
I don't think the abends are because of quick disconnects. You are abending with 0c1/AKEA abends. Check this which explains about 0C1 abends
| Code: |
0C1
System ABEND: S0C1
Description: An attempt was made to execute an invalid machine
instruction operation code. The operation code is either
invalid or is for an instruction that is not available on
this CPU.
This failure is usually due to a branch to an invalid storage
location, as might occur in a load module with unresolved
external references, or when a branch to an address outside
of a program occurs. (Reason Code 1)
User Action: Correct the program logic or construction error and resubmit
the job. Possible causes for this abend include:
Amode was set to 24, but a branch was attempted to a
31-bit or (on z/OS) a 64-bit address
In assembler, coding 'B R14' when you meant to code 'BR R14'
Subscript error occurred
"Clobbered" code; i.e., the executing program was
corrupted in virtual storage and then a branch was
performed into the corrupted code
Tried to read a file that was not open
Misspelled DDNAME followed by attempted I/O to same file
Error in parameters passed to subroutines
Missing DD card followed by attempted I/O to same file
Recording mode was wrong, or density was incorrect
Bad load module, possible bad object deck in FORTRAN
(unresolved external references)
Missing dimension statement
Same name for an array and a subroutine
COBOL: subroutine prog ID was the same as the entry name
tried to call within COBOL sort I/O procedure
tried to call a subroutine which could not be found
incomplete DCB for SORTIN file
using sort verb, DDNAME was not SORTOUT when the
"giving" option was used.
executing sort-using after opening SORTIN file
|
Hope this helps...
Cheers
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
