Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Compatibility for STR FDM v7.2.0 and Cobol for z/OS and OS/390 v3.1
++PTF(P720ZOT) . ++VER(Z038) FMID( PDSE 720) . ++ZAP(STARTOOL) /*
CMS-XML FDM730: In HIST command, support for COBOL for z/OS and OS/390 V3.1 compiler
++PTF(P730ZOT) . ++VER(Z038) FMID( PDSE 730) . ++ZAP(STARTOOL) /*
CMS-XML km-dim 10 : build Z/os : how is handled relationships between cobol sources and cobol copybooks ?
In TEMPLATE(MDHBSBM0), change the DDNAME MDHSBOM to point at a dataset you have created for the purpose. It needs to be a PDSE , with LRECL=1024, RECFM=VB. Then after a build, this dataset will be filled with members each of which is a BOM, The member name refers to the step number of the build that this BOM relates to.
CMS-XML COBOL 5.2 support
COBOL 5.2 support
CMS-XML Cobol internal data section is unavailable
Cobol internal data section is unavailable
CMS-XML Poor response scrolling in Cobol Working Storage Section
Poor response scrolling in Cobol Working Storage Section
CMS-XML STR: Locate load members compiled with COBOL translators
STR: Locate load members compiled with COBOL translators
CMS-XML display cobol pgm from storage display in starspy/390
display cobol pgm from storage display in starspy/390
CMS-XML XML Yellow COBOL copybooks for ZMF 8.2 Patch 4
XML Yellow COBOL copybooks for ZMF 8.2 Patch 4
CMS-XML XML Yellow COBOL copybooks for ZMF v8.1.4
XML Yellow COBOL copybooks for ZMF v8.1.4
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs