You will know that it is up by a couple of ways. 1) From the started task log, you should see messages like below:
EPW0051I FFSTFFDC: INITIALIZATION OF FFST/FFDC COMPLETE EPW0201I EPWFFST: INITIALIZATION OF FFST/ESA IN PROGRESS EPW0505I EPWFFST: FFSTPARM MEMBER START00 NOT FOUND EPW0505I EPWFFST: FFSTPARM MEMBER TRNSABCD NOT FOUND EPW0202I EPWFFST: INITIALIZATION OF FFST/ESA COMPLETE EPW0505I EPWFFST: FFSTPARM MEMBER EPWHWR01 NOT FOUND EPW0509I EPWFFST: NOW USING LOGID FFSTLOG1 EPW0250I EPWPITSK: FFST INITIALIZATION FOR FFSTV1R2 COMPLETE EPW0250I EPWPITSK: FFST INITIALIZATION FOR VTAM COMPLETE EPW0250I EPWPITSK: FFST INITIALIZATION FOR TCP COMPLETE EPW0250I EPWPITSK: FFST INITIALIZATION FOR CSM COMPLETE 2) You should also have some datasets allocated (CKPT, DUMP, LOG1, LOG2 & PARMLIB). The LOG will give you more detail information from its processing and if a dump was taken within FFST, it should be in the DUMP dataset. Craig -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, September 18, 2014 14:04 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Help with FFST/MVS and the first failure symptoms component? For the shops I have worked at, I did not setup ffsti am not sure there is a need for it. Lizette -----Original Message----- >From: "Hansen, Dave L - Eagan, MN" <dave.l.han...@usps.gov> >Sent: Sep 18, 2014 11:46 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Help with FFST/MVS and the first failure symptoms component? > >Dear Big Iron People, > > (Still waiting to get on the CICS-L list) > > FFST/MVS (First Failure Support Technology/MVS): > http://pic.dhe.ibm.com/infocenter/zos/v2r1/index.jsp?topic=%2Fcom.ibm.zos.v2r1.e0za100%2Fe0za10015.htm > >Q1). How do we know if we are taking advantage of FFST/MVS? Where can I >look, or what can I enter to know if we have FFST enabled? > > > CICS says a program might call the first failure symptoms component. It's > documented in the CICS TS for z/OS 5.1 Installation Guide in Chapter 30. MVS > ASREXIT - SYMREC Authorization Exit. > > I read the CICS Problem Determination Guide. There are quite a few > references to first failure: > > General CICS tracing is handled by the CICS trace domain. It traces >the flow of execution through CICS code, and through your applications >as well. You can see what functions are being performed, which >parameters are being passed, and the values of important data fields at >the time trace calls are made. This type of tracing is also useful in >first failure data capture, if an exception condition is detected by CICS. > > In addition, exception trace entries are always written to the >internal trace table, even if no trace destinations are currently >started. Other trace destinations that are currently started get the >exception trace entry as well, but the entry always goes to the >internal trace table even if you have turned tracing off completely. This >function provides first failure data capture. > > CICS exception tracing is always done by CICS when it detects an >exception condition. The sorts of exception that might be detected >include bad parameters on a domain call, and any abnormal response from >a called routine. The aim is "first failure data capture", to record >data that might be relevant to the exception as soon as possible after it has >been detected. > > It may just look like they could be related. I didn't find a section in > the CICS manuals (yet) about a CICS "first failure symptoms component". > >Q2). Does anyone know if CICS "first failure" has interactions with FFST/MVS? > Also would you know where I can find more information on this CICS "first >failure symptoms" component? > > > Thanks, Dave > > > > > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ________________________________ This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
