In order to offer any suggestions on this, I need more information.What language is your CICS program and are you using LE? What version of the compiler is in use? And what compiler options are being specified? What version of z/OS and the Z/OS Debug Tool are in use.Are CICS programs compiled outside of ZMF able to have Debug breakpoints specified? Breakpoints are generally established by the compiler options in use to set runtime hooks. If CICS programs compiled outside of ZMF are are able to have breakpoints established then you may want to compare the compiler options in your ZMF specific JCL and your non ZMF compiler JCL. Using XPED transaction with Changeman CICS Xpeditor option to 'y' while compiling. The Disadvantag of CEDF is if the transaction abends exit from the trasaction is no. How are you invoking the Debug facility in CICS? DTCN transaction? David Jackson. Write a reply I have seen this before. The IBM DEBUG facility in COBOL hard codes the name of the DEBUG dataset in the Load Module. If the ChangeMan standard process is being followed where we create the DEBUG file in a temp dataset -- that is the dataset that is being stored inside the load module and since it is temproary its not there at execution time. I would think there is a way to override the dataset at test time but I am not aware of it and the customer I was working with wasn't either. The reason we store it in a temproary file is so BAT90 will get the right module associated with the source -. The work around we did was to create the DEBUG file directly in the package and then copy it out to a temporary dataset for BT90 analysis. I am sure we could have just created the control cards manually. You cannot use the Compuware Xpediter.LST file to debug a program with CA Intertest CICS. You must use a PROTSYM listing member to debug. CA Intertest CICS has a post processing program called IN25COB2 which takes the Standard IBM COBOL compiler output and creates a PROTSYM repository member from the compile output. Then the PROTSYM source code member is used with CA Intertest CICS to debug the program. IN25COB2 also REQUIRES certain compiler options to be in effect to post process the listing. The following compiler options are required to load symbolic information for COBOL programs into the PROTSYM file: Option Description MAP Produces a Data Division map. NONUMBER Suppresses compiler-generated line numbers. OFFSET or LIST* Produces a condensed Procedure map or full Assembler Procedure map. XREF Produces a cross-reference of data and procedure names. NOPT or OPT(0)** Produces breakpoints synchronized with source. NOSTGOPT Prevents the compiler from discarding unreferenced data items. The NOSTGOPT option is only valid for COBOL 5.1 and above. * The LIST option is required when using the integrated CICS translator or integrated SQL coprocessor of COBOL for z/OS. ** When a COBOL program is OPTIMIZED, your breakpoints may not get stopped exactly where you think they should because the optimization is adding or modifying the generated code, and it may not be synchronized with the related source statements in the listing. Unfortunately we do not know what the Compuware Xpediter.LST compile listing file looks like. The.LST file could be packed to save space or is not in a standard IBM listing format. The CA Intertest CICS development team has no control over future changes that may be made to the format of the.LST file which could cause the post processor IN25COB2 program to fail. You could try running the post processor IN25COB2 using the Xpediter.LST file as input to see if the.LST file can be converted into a PROTSYM member which could then be used to debug the program with CA Intertest CICS. Officer and a gentleman free. Below is the basic JCL to post process a compile listing with IN25COB2. JOBCARD //JOBLIB DD DISP=SHR,DSN=INTERT10.GA.CAVHLOAD //POSTPRO EXEC PGM=IN25COB2 //SYSUDUMP DD SYSOUT=* //INPUT DD DISP=SHR,DSN=Xpediter.LST file //OUTPUT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=3990) //MESSAGE DD SYSOUT=* //PROTSYM DD DISP=SHR,DSN=INTERT10.PROTSYM //CARDS DD * PROGNAME,LISTER=ALL /* // If you encounter post processing errors while running IN25COB2 you may consider opening a case with CA technical support and provide the provide the requested documentation.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. Архивы
Март 2019
Категории |