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 STR710: VERIFY : NOLOAD results in PDS999E ABEND S80A U0000 AT +005FC6 IN PROGRAM PDSSPACE
REP 3C 47F0,C774 ** 1249 B LOCRC0 REP 42 3A9C 1249 DC AL 2(300*50+4) REP 012C 47F0,C02E 1243 B PATCH
CMS-XML STR610: STARTOOLS directory entry (DIRENT) display is incorrect
0000001B PDS2FTBL DS FL2 - LENGTH OF FIRST BLOCK OF TEXT 0000001D PDS 2EPA DS AL 3 - ENTRY POINT ADDRESS ASSOCIATED 00000020 PDS2FTBO DS 0BL3 - FLAG BYTES (AOS USE OF FIELD)
PDF Serena StarTool FDM Reference Guide
... DIAPANL@DIAPART@DIASTAK @DIATBL @DIAWRK ALLGLOB ASMEXT2 CHECKOUTCICS COMPARE COMPARESCOMPA1 COMPA2 COMPA3 DISAMSM DISAMXM DISASME DISASMX DISASM3 MAPXREF PDS 99 PDS 99T1DTESTMSG >----->pdia @DIACLIK@DIAINIT@DIALOG @DIAPANL@DIAPART@DIASTAK @DIATBL @DIAWRK >----->pal/ @DIALOG ALLGLOB >----->pob/ al ALLGLOB >----->pdis* DISAMSM DISAMXM DISASME DISASMX DISASM3 >--- ...
CMS-XML Unexpected SYNCH3 reported by audit on a PL1 load module; stored in PDS
A ZMF package contains an enterprise PLI load module in a PDS . When audit runs against this package, a SYNCH3 (unparseable) is reported on the PLI load module. If the load module is stored in a PDSE rather than a PDS, the SYNCH3 does not occur.
CMS-XML KM-Dim9: Reported Defect DEF83987: Garbage in compare result when comparing an item to a ZOS PDS member.
Garbage in compare result when comparing an item to a ZOS PDS member.
CMS-XML DSNBYDSN reporting 'insync' incorrectly for new members
SM COMPARE=DSNBYDSN is not correcctly reporting 'outsync po' on compare for new members added to a PDS . parameters used to create the fingerprint EXTENDED=YES
CMS-XML PDS052I real storage display is inaccurate
A CPU upgrade to a z/Series processor was done. The CONTROL LISTENV command does not report the same amount of real storage as the IBM command D M=STOR does. Shouldn't FDM be reporting real storage as 768M?
CMS-XML OPT field missing in USAGE report
STARTOOL 'IL.TSS.ND64' USAGE PDS 200I DISP UNIT OPT RECFM LRECL BLKSIZE ALLOCTRK FREETRK SECONDARY FREEDIR
CMS-XML PDS224I incorrectly show non-SMS dataset as authorized
Product: StarTool FDM Problem: FDM is incorrectly reporting the APF-authorized status of a library. - MVS is executing with APF FORMAT(DYNAMIC)
CMS-XML Dim10: Reported Defect: Zos issue - authentication failed on first command call
Running an FI in desktop client to an MVS PDS , prompts for a remote node login, it works fine however it produces an error: Get Item - MDHPRG4500325E Error: User authentication failed Even though the FI does work.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs