|
View previous topic :: View next topic
|
| Author |
Message |
Ali_gezer
Active User
Joined: 06 Apr 2021
Posts: 123
Location: argentina
|
|
|
|
Hello, how are you?
is there a way to know which file is used to back a cics transaction? There is no one in my team that can give me that info.
I searched the forum but I did not find a clue or answer.
Thanks in advance. |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
The simplest way to find any ddname used in a CICS transaction is to read the source code of the programs for that transaction. The developer or application documentation would also be useful.
Garry. |
|
| Back to top |
|
|
Ali_gezer
Active User
Joined: 06 Apr 2021
Posts: 123
Location: argentina
|
|
|
|
| Garry Carroll wrote: |
The simplest way to find any ddname used in a CICS transaction is to read the source code of the programs for that transaction. The developer or application documentation would also be useful.
Garry. |
Is a cobol cics. I did not find the dd name because of that. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
It doesn't matter what language the program is, there would be one or more 'EXEC CICS' statement(s) with 'FILE(ddname)'.
The 'ddname' specified is either a constant or a working storage variable that is assigned.
Another, potentially more tedious option would be to step through the transaction using CEDF.
Garry. |
|
| Back to top |
|
|
Ali_gezer
Active User
Joined: 06 Apr 2021
Posts: 123
Location: argentina
|
|
|
|
| Garry Carroll wrote: |
It doesn't matter what language the program is, there would be one or more 'EXEC CICS' statement(s) with 'FILE(ddname)'.
The 'ddname' specified is either a constant or a working storage variable that is assigned.
Another, potentially more tedious option would be to step through the transaction using CEDF.
Garry. |
first forgive me because im cics begginer.
I have a screen that when you enter some input it will enter a vsam file and bring back certain records. The thing is that the cobol cics program that makes this cics screen do not have any reference to the vsam name.
I dont expect you to bring me the solution but maybe you can give me a clue where to find. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
| Code: |
| CEMT I FIL DSN(dsn-name) |
Did it not give? |
|
| Back to top |
|
|
Ali_gezer
Active User
Joined: 06 Apr 2021
Posts: 123
Location: argentina
|
|
|
|
| Rohit Umarjikar wrote: |
| Code: |
| CEMT I FIL DSN(dsn-name) |
Did it not give? |
I did it with the file I suspect is the vsam that backs de bics screen but it only show me some data but it do not show me to what cics is related.
I need to confirm the name of the file that backs that cics screen to know how this file is created in cobol because it has errors. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| wouldn' it be simpler to read the application development documentation ??? |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
| I have a screen that when you enter some input it will enter a vsam file and bring back certain records. The thing is that the cobol cics program that makes this cics screen do not have any reference to the vsam name. |
The cobol program will not have the vsam name, it will have a ddname which is associated with the vsam file. The CEMT I FIL(vsamname) would show the ddname referenced in the program.
| Quote: |
| I did it with the file I suspect is the vsam that backs de bics screen but it only show me some data but it do not show me to what cics is related. |
Guessing which file is behind a CICS transaction is not a good approach.
If you don't have the necessary documentation, read the source of the program associated with the transaction ( CEMT I TRAN(xxxx) will give you this). If the program doesn't have the 'EXEC CICS' statements with 'FILE(ddname)', check any called programs or programs it LINKs/XCTLs to.
Failing the above, start an EDF session (enter CEDF in the CICS screen) and then enter the transaction. This will let you step through the code and you will eventually see the EXEC CICS statement specifying the ddname. As I said earlier, this can be quite tedious.
Garry. |
|
| Back to top |
|
|
Ali_gezer
Active User
Joined: 06 Apr 2021
Posts: 123
Location: argentina
|
|
|
|
| Garry Carroll wrote: |
| Quote: |
| I have a screen that when you enter some input it will enter a vsam file and bring back certain records. The thing is that the cobol cics program that makes this cics screen do not have any reference to the vsam name. |
The cobol program will not have the vsam name, it will have a ddname which is associated with the vsam file. The CEMT I FIL(vsamname) would show the ddname referenced in the program.
| Quote: |
| I did it with the file I suspect is the vsam that backs de bics screen but it only show me some data but it do not show me to what cics is related. |
Guessing which file is behind a CICS transaction is not a good approach.
If you don't have the necessary documentation, read the source of the program associated with the transaction ( CEMT I TRAN(xxxx) will give you this). If the program doesn't have the 'EXEC CICS' statements with 'FILE(ddname)', check any called programs or programs it LINKs/XCTLs to.
Failing the above, start an EDF session (enter CEDF in the CICS screen) and then enter the transaction. This will let you step through the code and you will eventually see the EXEC CICS statement specifying the ddname. As I said earlier, this can be quite tedious.
Garry. |
Thank you for your help, I found it, the name was in the working storage and then using the CEMT I FIL command I can find the alias of the file.
Thank you again and thans to the rest. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
Thanks for letting us know.
Garry. |
|
| Back to top |
|
|
|
|
