Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Need clarification of VSAM FCT and DFHCSD relation

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS
View previous topic :: :: View next topic  
Author Message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Sun Apr 10, 2016 1:06 am    Post subject: Need clarification of VSAM FCT and DFHCSD relation
Reply with quote

Dear All,

In my application i find few VSAM files used in CICS COBOL programs were not having DSN name defined. I used CEMT I FILE() command to check the presence of DSN name in the CICS region but i could not get the DSN name and FCT entries. I checked the file name in CSD file, dsn nsme is not present. Apart from FCT, is there anyway that VSAM file can be accessed ( i dont think so) since i am not a system programmer i need clarification on this Also i read through IBM manuals regarding dynamically defining FCT for VSAM, Is there any chance multiple filename can be defined for one VSAM DSN? Is there anyway to check the presence of DSN of VSAM apart from CEMT I FILE and searching in CSD?
Back to top
View user's profile Send private message

Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 1610
Location: NY,USA

PostPosted: Sun Apr 10, 2016 6:10 am    Post subject:
Reply with quote

Send an email to CICS Admin at your site. They should be able to help you.
Have you check the CICS JCL? you can override the DSNAME at run time by specifying the DD name and DSNAME for the file which will use the provided value.
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Sun Apr 10, 2016 4:46 pm    Post subject:
Reply with quote

Hi Rohit,

If CICS JCL dynamically overrides the DSN name, will be it impacts FCT? I will check the CICS JCL.
Back to top
View user's profile Send private message
Eyal.ma

New User


Joined: 05 May 2013
Posts: 5
Location: Israel

PostPosted: Mon Apr 11, 2016 1:12 pm    Post subject:
Reply with quote

You need to understand that there are 3 places you can define a file. FCT, CSD and CICS JCL.

All those 3 options, are not dynamic. So any dynamic change, will not affect them the next time the CICS restarts.

A file can be defined multiple times with a different DSN name (CSD, FCT and JCL). The JCL dataset name definition takes precedence over the DSNAME of the FCT or CSD.

If you dynamically change the name of the dataset of the tile, next time the CICS restarts, if the definition is in the CICS JCL or the FCT, it will overwrite what was defined dynamically.
If the definition of the dataset name is in the CSD, it will be overwritten only if the CICS starts in COLD status (or initial).

I hope this helps.
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Mon Apr 11, 2016 1:20 pm    Post subject:
Reply with quote

The below is the CICS JCL, please let me know where can i find the VSAM file to be overridden?
Code:


//XXXXXXXX JOB MSGCLASS=L,MSGLEVEL=1                                   
//*                                                                     
//*------------------------------------------------------------------- 
//*  CICS Transaction Server for z/OS Version 5 Release 2               
//*------------------------------------------------------------------- 
//*                                                                                         
//*                                                                     
//*------------------------------------------------------------------- 
//*  STCPROC:  SYS1.TNDT.STCPROC                                       
//*------------------------------------------------------------------- 
//*                                                                     
//*PROCLIB  JCLLIB ORDER=(SYS3.CICS.DMT1.V690.PROCLIB)                 
//*                                                                     
//REDEFTD  EXEC PGM=IDCAMS                                             
//SYSPRINT DD SYSOUT=*
//SYSIN    DD DSN=SYS3.CICS.DMT1.V690.PARMLIB.UTV(MU8INTRA),DISP=SHR   
//*                                                                     
//XXXXXXXX PROC S=COLD,                < S=AUTO | COLD | INITIAL       
//   REG=0M,                           < Region Size                   
//   DFHSIT=10,                        < DFHSITnn: nn=00-99             
//   MVSID=DMT1,                       < MVS &SYSNAME: 4 karakterer     
//   ENVID=DMT1,                       < MVS-, kunde-, Plexident       
//   PTFID=UI30599,                    < TS   PTF-nivå                 
//*  XPTFID=UI30599,                   < CPSM PTF-nivå                 
//*  RPTFID=UI30599,                   < REXX PTF-nivå                 
//*  APTFID=UI30599,                   < CIAZ PTF-nivå                 
//*  GPTFID=UI30599,                   < CTG  PTF-nivå                 
//   CID=MU8,                          < CICS-ident: 3 karakterer       
//   ALEV=.UTV                         < .TEST / .UTV / blank for prod 
//*                                                                     
//*SWLEVEL  INCLUDE MEMBER=TSSWL       < Overstyrer *PTFID= under PROC 
//*                                                                     
//CICS     EXEC PGM=DFHSIP,REGION=&REG,TIME=1440,                       
//         PARM=('SIT=&DFHSIT,START=&S,SYSIN')                         
//*                                                                     
//SYSIN    DD DSN=SYS3.CICS.&ENVID..V690.PARMLIB&ALEV(&CID.SIT), 
//            DISP=SHR                                               
//*                                                                   
//STEPLIB  DD DSN=SYS3.CICS.V690.&PTFID..SDFHAUTH,DISP=SHR           
//         DD DSN=SYS1.ACF2.ACF2LOAD,DISP=SHR                         
//         DD DSN=SYS1.TCPIP.SEZALNK2,DISP=SHR                       
//         DD DSN=SYSIT.T1I1.DRALIB,DISP=SHR                         
//         DD DSN=SYSIT.IMSM.RESLIB,DISP=SHR                         
//         DD DSN=SYSD.DB2.T1DU.SDSNEXIT,DISP=SHR                     
//         DD DSN=SYSD.DB2.T1DU.SDSNLOAD,DISP=SHR                     
//         DD DSN=SYS1.MQ.MU01.SCSQANLE,DISP=SHR                     
//         DD DSN=SYS1.MQ.MU01.SCSQAUTH,DISP=SHR                     
//         DD DSN=SYS3.TMON.CICS.T1.TCELOAD,DISP=SHR                 
//         DD DSN=SYS3.TMON.CICS.T1.LMKLOAD,DISP=SHR                 
//         DD DSN=SYS3.TMON.CICS.T1.LMKRLOD,DISP=SHR                 
//*-------------------------------------------------------------------
//*        CICS Bibliotek                                             
//*-------------------------------------------------------------------
//DFHRPL   DD DSN=SYS3.CICS.&MVSID..V690.RES.PGMLOAD,DISP=SHR         
//         DD DSN=NU973.Z1LMBNER.CICLOAD.MCTP,DISP=SHR    *** NY MCTP
//         DD DSN=SYS3.CICS.&MVSID..V650.RES.PGMLOAD,DISP=SHR         
//         DD DSN=SYS3.CICS.&MVSID..V690.PGMLOAD,DISP=SHR             
//         DD DSN=SYS3.CICS.&ENVID..V690.TABLOAD&ALEV,DISP=SHR         
//         DD DSN=SYS3.CICS.V690.&PTFID..SDFHLOAD,DISP=SHR             
//*------------------------------------------------------------------- 
//*        CICS Programvare Bibliotek                                   
//*------------------------------------------------------------------- 
//         DD DSN=SYS1.ACF2.ACF2RPL,DISP=SHR                           
//         DD DSN=SYS3.CICS.ACF2.PGMLOAD,DISP=SHR                       
//         DD DSN=SYS3.CICS.ACF2RPL,DISP=SHR                           
//         DD DSN=NU741.Z1SYBNER.CICS.V620.CICSLOAD,DISP=SHR           
//         DD DSN=NU741.Z1SYBNER.CICSLOAD,DISP=SHR                     
//         DD DSN=SYS1.CEE.SCEECICS,DISP=SHR                           
//         DD DSN=SYS1.CEE.SCEERUN2,DISP=SHR                           
//         DD DSN=SYS1.CEE.SCEERUN,DISP=SHR                             
//         DD DSN=SYS1.MQ.MU01.SCSQANLE,DISP=SHR                       
//         DD DSN=SYS1.MQ.MU01.SCSQCICS,DISP=SHR                       
//         DD DSN=SYS1.MQ.MU01.SCSQAUTH,DISP=SHR                       
//         DD DSN=SYS1.MQ.MU01.SCSQLOAD,DISP=SHR                       
//         DD DSN=SYS3.TMON.CICS.T1.TCELOAD,DISP=SHR                   
//         DD DSN=SYS3.TMON.CICS.T1.LMKLOAD,DISP=SHR                   
//         DD DSN=SYS3.TMON.CICS.T1.LMKRLOD,DISP=SHR                   
//         DD DSN=SYS1.COMPWARE.CICS.SLCXLOAD,DISP=SHR                 
//         DD DSN=NU523.Z1LMBNER.TABLOADX,DISP=SHR                     
//         DD DSN=NU523.Z1LMBNER.SIMRLODC,DISP=SHR                     
//         DD DSN=NU523.Z1LMBNER.SIMRLODB,DISP=SHR                     
//         DD DSN=NU523.Z1LMBNER.SDSLLODC,DISP=SHR                     
//         DD DSN=NU523.Z1LMBNER.SDSLLODB,DISP=SHR                     
//         DD DSN=NU973.Z1LMBNER.CICLOAD,DISP=SHR                       
//         DD DSN=NR973.Z1LMBNER.CICLOAD,DISP=SHR                       
//         DD DSN=NU794.Z1LMBNER.PP420.CICSLOAD,DISP=SHR               
//*------------------------------------------------------------------- 
//*        CICS Messages and Codes datasett                             
//*------------------------------------------------------------------- 
//DFHCMACD DD DSN=SYS3.CICS.V690.&PTFID..SDFHCMAC,DISP=SHR             
//*------------------------------------------------------------------- 
//*        CICS Systemdatasett / Default                               
//*------------------------------------------------------------------- 
//DFHAUXT  DD DSN=SYSC.CICS.&CID..V690.DFHAUXT,DISP=SHR                 
//DFHBUXT  DD DUMMY                                                     
//DFHCXRF  DD DSN=SYSC.CICS.&CID..V690.DFHCXRF,DISP=SHR                 
//DFHDMPA  DD DSN=SYSC.CICS.&CID..V690.DFHDMPA,DISP=SHR                 
//DFHDMPB  DD DUMMY                                                     
//DFHGCD   DD DSN=SYSC.CICS.&CID..V690.DFHGCD,DISP=SHR,                 
//            AMP=('BUFND=33,BUFNI=32,BUFSP=1114112')                   
//DFHINTRA DD DSN=SYSC.CICS.&CID..V690.DFHINTRA,DISP=SHR               
//DFHLCD   DD DSN=SYSC.CICS.&CID..V690.DFHLCD,DISP=SHR                 
//DFHTEMP  DD DSN=SYSC.CICS.&CID..V690.DFHTEMP,DISP=SHR                 
//CMSYXRF  DD DSN=SYSC.CICS.&CID..V690.DFHCXRF,DISP=SHR                 
//*------------------------------------------------------------------- 
//* NB!!!  Fast rekkefølge for SYSOUT=F. Rekkefølgen er viktig for     
//* NB!!!  å gi offshore brukere tilgang til å se på appl. data i       
//* NB!!!  CICS STC-tasker, DD-name CICSRESM og CEEMSG.                 
//*------------------------------------------------------------------- 
//CICSRESM DD SYSOUT=F                                                 
//CEEMSG   DD SYSOUT=F                                                 
//*------------------------------------------------------------------- 
//*        CICS Sysoutdatasett / Default                               
//*------------------------------------------------------------------- 
//ABNLIGNR DD DUMMY                                                     
//INTRDR   DD SYSOUT=(A,INTRDR)                                         
//BCINTRDR DD SYSOUT=(A,INTRDR)                                         
//DADCSUBM DD SYSOUT=(A,INTRDR)                                         
//KVINTRD  DD SYSOUT=(A,INTRDR)                                         
//SYSABEND DD DUMMY                                                     
//LOGUSR   DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)             
//MSGUSR   DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)             
//PRINTER  DD SYSOUT=*                                               
//SYSOUT   DD SYSOUT=*                                               
//*-------------------------------------------------------------------
//*        ACF2                                                       
//*-------------------------------------------------------------------
//ACF2PARM DD DSN=SYS3.ACF2.&ENVID..PARMLIB&ALEV(ACF2STD),DISP=SHR   
//         DD DSN=SYS3.ACF2.&ENVID..PARMLIB&ALEV(&CID.A2P),DISP=SHR   
//ACF2LOG  DD SYSOUT=*                                               
//*-------------------------------------------------------------------
//*        TMON                                                       
//*-------------------------------------------------------------------
//LMRKPOS  DD DSN=SYXP.TMON.REPOSIT,DISP=SHR                         
//LMRKDPX  DD DSN=SYXP.TMON.REPOSDPX,DISP=SHR                         
//*-------------------------------------------------------------------
//*        TCPIP                                                     
//*-------------------------------------------------------------------
//SYSTCPD  DD DISP=SHR,DSN=SYS1.TCPPARMS(TCPDATA)                     
//*-------------------------------------------------------------------
//*        End of xxxxxxx                                       
 //*-------------------------------------------------------------------
 //         PEND                                                       
 //         EXEC xxxxxxx                                               
     
                                                 
Back to top
View user's profile Send private message
Eyal.ma

New User


Joined: 05 May 2013
Posts: 5
Location: Israel

PostPosted: Mon Apr 11, 2016 1:52 pm    Post subject:
Reply with quote

What VSAM file are you looking for?

Also I'm trying to figure maybe I read what you wrote wrong.

When you are using CEMT I FILE you don't see the file at all, or you don't see the DSNAME filled?

If you do CEMT I FILE and you don't see the file you are looking for at all, most likely it was not defined in any of the 3 locations possible, and you or the CICS admin needs to define the file.

If you see the file but no DSNAME at all, it means that either the FCT or CSD did not specify a dataset name, and someone do needs to.
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Mon Apr 11, 2016 2:44 pm    Post subject:
Reply with quote

Hello Eyal.ma,

In CEMT I File() i didn't get the DSN name. I have mentioned already


Quote:

I used CEMT I FILE() command to check the presence of DSN name in the CICS region but i could not get the DSN name and FCT entries

Read more: http://ibmmainframes.com/viewtopic.php?p=334733#334733#ixzz45VQvGSph


The VSAM read in API program is giving error , EIBRESP 19 & EIBRESP2 60, file not open, hence the DSN name is not available. So our team have decided to ignore the VSAM file for migration.

Thank you everyone for the reply.
Back to top
View user's profile Send private message
Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 1610
Location: NY,USA

PostPosted: Mon Apr 11, 2016 8:33 pm    Post subject:
Reply with quote

Always contact CICS support staff for these type of issues than making decisions based out of forum replies as they are not 100% true upon your shop standards.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Mon Apr 11, 2016 9:26 pm    Post subject:
Reply with quote

I echo Rohit's recommendation -- you REALLY need to contact your site support group. If, for example, your site is using MRO and you're looking at the TOR (Terminal-Owning Region) while the data set is defined in the FOR (File-Owning Region), then you won't necessarily see any link between the FCT and the DFHCSD entry -- partly because they are different CICS regions, and partly because the TOR and FOR could be using different DFHCSD data sets. And the data set name would be in the TOR, so you would not usually see it in the TOR.
Back to top
View user's profile Send private message
Eyal.ma

New User


Joined: 05 May 2013
Posts: 5
Location: Israel

PostPosted: Mon Apr 11, 2016 9:33 pm    Post subject:
Reply with quote

Robert Sample wrote:
I echo Rohit's recommendation -- you REALLY need to contact your site support group. If, for example, your site is using MRO and you're looking at the TOR (Terminal-Owning Region) while the data set is defined in the FOR (File-Owning Region), then you won't necessarily see any link between the FCT and the DFHCSD entry -- partly because they are different CICS regions, and partly because the TOR and FOR could be using different DFHCSD data sets. And the data set name would be in the TOR, so you would not usually see it in the TOR.


True.
But most likely in this case, the file will be specified as remote with no other settings.
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Fri Apr 15, 2016 7:58 pm    Post subject:
Reply with quote

I have checked all the regions CSD, all are region CICS JCL is representing the same CSD file.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Fri Apr 15, 2016 8:34 pm    Post subject:
Reply with quote

So what did your site support group tell you when you talked to them?
Back to top
View user's profile Send private message
Rohit Umarjikar

Senior Member


Joined: 21 Sep 2010
Posts: 1610
Location: NY,USA

PostPosted: Fri Apr 15, 2016 10:39 pm    Post subject:
Reply with quote

Quote:
The VSAM read in API program is giving error , EIBRESP 19 & EIBRESP2 60, file not open, hence the DSN name is not available. So our team have decided to ignore the VSAM file for migration.

CICS definition is incorrect for DSNAME
Have you looked for data tables yet?
Quote:
is there anyway that VSAM file can be accessed ( i dont think so) since i am not a system programmer i need clarification on this

TALK TO SITE SUPPORT
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Mon Apr 18, 2016 1:12 am    Post subject:
Reply with quote

Hi Rohita,

Could you please explain on data tables wrt to VSAM FCT? I have posted this to my support team.

Quote:

Have you looked for data tables yet?
Back to top
View user's profile Send private message
pkmurali
Warnings : 1

Active User


Joined: 15 Dec 2005
Posts: 236

PostPosted: Mon Apr 18, 2016 4:30 pm    Post subject:
Reply with quote

I got it.. Data tables

https://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.sysdefinition.doc/topics/dfha2_cics_datatables.html
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2502
Location: Atlanta, Georgia, USA

PostPosted: Mon Apr 18, 2016 4:35 pm    Post subject: Reply to: Need clarification of VSAM FCT and DFHCSD relation
Reply with quote

Data Tables (a fancy name for a VSAM file) is used (in my opinion) as Read-Only as writing to it will defeat its overall purpose.

Rather than define the FCT entry as a data-table, define it to an efficient LSR Pool as well as efficient CISIZE's for data and index. Your CICS Sysprog would probably be the person to consult with on this matter.

Data-Tables are moved to extended-storage at CICS startup and therefore, accessing records from them is much more efficient, as most VSAM path logic is eliminated.

You should Google "CICS Data Tables" and learn more about them.

HTH....
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CICS All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts BWO option in VSAM blayek CICS 3 Sat Nov 05, 2016 10:47 am
No new posts VSAM define for large file jerryte JCL & VSAM 9 Wed Oct 05, 2016 1:51 am
No new posts CICS VSAM RLS READ akodakka CICS 3 Tue Oct 04, 2016 3:09 pm
No new posts 2 vsam file compare and update a fiel... ABINAYATHULASI DFSORT/ICETOOL 6 Sun May 29, 2016 11:15 am
No new posts trying to define a VSAM Cluster in JCL t5590ag JCL & VSAM 10 Thu May 19, 2016 5:52 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us