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 Staging C++ load modules from PDS/E to PDS
Staging C++ load modules from PDS / E to PDS
CMS-XML Batch Stage from Dev of LOD from PDS to PDS/E fails
SELECT MEMBER=(CMNAS000) IEB1013I COPYING FROM PDS INDD=SYS00047 VOL=SRSM5A DSN=CMNSUP.INTL.CMN534.LOAD IEB1014I TO PDSE OUTDD=SYS00048 VOL=SRSMF3 DSN=CMNSUP.INTL.DEMO.STG2.#000652.LOD
CMS-XML Checkout to personal library with 'Library dsorg' of 'PDSE' getting 'CMN2345a - Target data set is a PDS(E), target DSORG must be PDS(E)'
When checking out to a personal library and on panel CMNCKOT3 you enter 'PDSE' for field 'Library dsorg' you get the short message 'INVALID TARGET DSORG' and the long message 'CMN2345A - Target data set is a PDS(E), target DSORG must be PDS(E)'. If you change this to ' PDS ' it works.
CMS-XML Testing if a PDS(E) member exists in a HLLX routine
/* */ memberCK = BPXWUNIX('head -1 "//''MY. PDS .TOCHECK(EXISTS)''"') say "MY.PDS.TOCHECK(EXISTS) RC = "memberCK
CMS-XML S0C7 in SERDATES when running cmnfixmn using PDS-E baseline librar
S0C7 in SERDATES when running cmnfixmn using PDS - E baseline librar
CMS-XML S0C4-04 CMNVRARE+19E08 running RLSMAREA.PACKAGE.CHECKIN XML Service
A release contains a combination of like- PDS , like-SRC and also java source components held in zFS
CMS-XML SER0953E Task abnormally terminated: Comp=S0C4 Function=STAGE/COPY
When checking out a large member from a PDS baseline dataset to a PDSE staging dataset cause the following abend. IEC032I E37-04,IGC0005E,SERSUP6O,S610ALL,SYS00078,3D96,SRSMA8,CMNSUP.CD.S610ALL.DIMT.#000008.CPY
CMS-XML 0C4-11 HPSVINIT+A36 using SSV after coversion from PDS to PDSE staging libs
TIME=18.05.10 SEQ=04343 CPU=0000 ASID=01BA PSW AT TIME OF ERROR 478D1000 8014358 E ILC 4 INTC 11 ACTIVE LOAD MODULE ADDRESS=00142B58 OFFSET=00000A36
CMS-XML CMN30PDS copying release package members from wrong dataset
Whilst the contents should be identical in most situations, there are opportunities for them to differ. Therefore, to err on the side of caution, the release staging datasets are also used in the baseline ripple process (i. e . CMN30 job).
CMS-XML Problems with PDS files filling up in the promotion systems
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SYSUT1 in the above example would point to &PROMDS Warning: This approach will fail for any promotion libraries that are allocated to started tasks (i. e . CICS, CMN).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs