|
View previous topic :: View next topic
|
| Author |
Message |
dudenithy
New User
Joined: 02 Mar 2012
Posts: 48
Location: India
|
|
|
|
Hi,
I would like to know the user ID who is deallocating (closing) the file in CICS. I could able to see the entries in SDSF log under MSGUSER sysout, but always module as DFHDCN as below.
| Code: |
DFHFC0200 04/19/2013 09:48:20 NATBEITA Non-RLS file CPPLT has been allocated to data set AT.EI.SITBE.CIA20V.CPPLTA. Module DFHFCN.
DFHFC0200 04/19/2013 09:48:20 NATBEITA Non-RLS file CPPLTA has been allocated to data set AT.EI.SITBE.CIA20V.CPPLTA. Module DFHFCN.
DFHFC0201 04/19/2013 09:50:02 NATBEITA Non-RLS file CPPLT has been deallocated. Module DFHFCN.
DFHFC0201 04/19/2013 09:50:02 NATBEITA Non-RLS file CPPLTA has been deallocated. Module DFHFCN. |
Could anyone know where to find the user ID who is deallocate/allocate in CICS. Is there any log to see the same.
Thanks for your answer. |
|
| Back to top |
|
 |
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Is the file deallocation being performed using native CEMT commands or via a CICS-SPI API (such as SET FILE) or via a 3rd-party product, such as CAFC?
There is a GLUE exit for CEMT as well as the CICS-SPI API and your CICS System Programmer or Tech Support personnel would have to write a GLUE exit-program, where the USERID can be captured.
Take a look at the Customization Guide for your particular CICS Version/Release for the GLUE exit or look for an example in the CICS-supplied SDFHSAMP PDS.
There are also SMF records as well. |
|
| Back to top |
|
|
dudenithy
New User
Joined: 02 Mar 2012
Posts: 48
Location: India
|
|
|
|
hi Bill,
I need the information for both options, whoever using CEMT command directly, and also whoever closes the file through batch process (in which initially they will close the file and start batch processing). |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Are you using a 3rd-party product (such as CAFC) to CLOSE/OPEN VSAM Files or are you using a home-grown EXCI-Interface from Batch?
After further review, GLUE "XPCFTCH" maybe what you need and address DSECT "DFHUEPAR", label "UEPUSER" in the user-defined Exit-Program.
This GLUE is driven to in CICS prior to a LINK-API.
However, if you're using SPI-API's (such as SET FILE), review GLUE "XEISPIN" which is invoked before the SPI-API is executed and address label "UEPUSID" in the user-defined Exit-Program, again DSECT "DFHUEPAR".
Note: GLUE Exit-Programs are not for the faint of heart and requires good Assembler and CICS knowledge and certainly can't be taught via this forum.
You still need to give us some idea as to the Batch method being used. It may be as easy as extracting the &USER assignment, from the Batch Job-Card as demonstrated in the following callable Assembler sub-program -
ibmmainframes.com/viewtopic.php?p=296785&highlight=#296785
The following link demonstrates extracting Batch Job-Card information -
www.ibmmainframes.com/viewtopic.php?p=167434&highlight=#167434
If you can extract all this information in the Batch program and log it prior to the EXCI/DPL to the target CICS region, then you have the ability to find the culprit.
HTH.... |
|
| Back to top |
|
|
|
|
