View previous topic :: View next topic
|
Author |
Message |
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi All,
When I try to create DDIO using xpediter I am getting the following error. Pls help.
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECA FOR CSWCNSA.CO
BOL.DDIO, SMC004, 1
SVM4855I SET SECONDARY SPACE USING 70% OF PRIMARY ( 2 TRKS) : 1 TRKS
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECR FOR CSWCNSA.CO
BOL.DDIO, SMC004, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECR FOR CSWCNSA.CO
BOL.DDIO, SMC016, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECR FOR CSWCNSA.CO
BOL.DDIO, SMC017, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECR FOR CSWCNSA.CO
BOL.DDIO, SMC012, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
SVM4000I CSWCNSA, RACFSTD.RACFSTD, SYS00287, ATTEMPTING SPACSECR FOR CSWCNSA.CO
BOL.DDIO, SMC001, 123
SVM4001I RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA
IEC028I 837-08,IFG055 ,CSWCNSA,RACFSTD,SYS00287,971E,SMC001,CSWCNSA.COBOL.DDIO
*** |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
the third variable in you input screen is invalid |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
How did you define the DDIO? The x37 is usually a space problem but since you have a lot of other things in your post, it's hard to be sure. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Pls find the steps that I followed to create a file and let me know if I made any mistake.
I appreciate your help. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8796 Location: Welsh Wales
|
|
|
|
1) DO NOT post attachments as not every user is permitted to open them, thus reducing the number of people able to help you.
2) SVM4000I is a message issued by the BMC product StopX37 - so maybe you should look at space allocations |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
You need to contact your site support group for assistance. I suspect the space you are attempting to give the DDIO file is not available due to site constraints. Only your site support group can assist you in getting the DDIO file set up correctly. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Thank you All. I will check here with system team. Meantime if there is anything else I need to do pls post. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
I was trying to create the ddio using the utility CWDDSUTL, but the job is failing with S213.
SYSTEM COMPLETION CODE=213 REASON CODE=000000C8
TIME=08.57.29 SEQ=21849 CPU=0000 ASID=00BB
PSW AT TIME OF ERROR 075C1000 80E66226 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00E66220 - 41003B92 0A0D41F0 38BE56F0
AR/GR 0: 00CDCAB0/00E66504 1: 00000000/A4213000
2: 00000000/00007CB8 3: 00000000/00E65972
4: 00000000/007B9410 5: 00000000/007B97A4
6: 00000000/007B974C 7: 00000000/007B97A4
8: 00000000/007B976C 9: 00000000/007BACA8
A: 00000000/00E67414 B: 00000000/00E68B1C
C: 00000000/80E68BFC D: 00000000/007B96D0
E: 00000000/80E65AAA F: 00000000/000000C8
END OF SYMPTOM DUMP
using the job:
//UTILITY EXEC PGM=CWDDSUTL,REGION=4M,COND=(8,LT)
//*STEPLIB DD DISP=SHR,DSN=SYS5.XPEDITER.LINKLIB NOT VALID ANYMORE
//ABNLDFIL DD DISP=SHR,DSN=CSWCNSA.XPED.DDIO
//ABNLREPT DD SYSOUT=*
//ABNLTERM DD SYSOUT=*
//ABNLPARM DD *
FORMAT TYPE=SOURCE,GC=8,EXTENTS=460,AD=DUPS,RC=100,BLK=4096
DIRX
/*
//
//* EXTENTS=460 IS MAXIMUM EXTENTS NUMBER, 256 IS ABOUT AVERAGE |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
ok, responding to your next post.
first, I would try to generate a DDIO with much smaller allocations.
if that does not work, then
I would then get with your support group, as they tailor the jcl to be generated for the creation of DDIO files. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi Dick,
I use the same however getting the error which I posted at the top. (first post) |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
ibmmainframe1,
see my previous post, I have edited it and changed my remarks. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
There is definitely something wrong with the way you are building your DDIO. A 213-C8 means
Quote: |
C8
An attempt was made to open a compressed data set for update. The update option is not supported for compressed data sets. |
I use VSAM DDIO files so I can't really say much about the sequential DDIO files. However, I did find the Ccmpuware recommended batch job to allocate a new sequential DDIO file:
Code: |
//**********************************************************************
//* *
//* CXALLDS - JCL TO ALLOCATE THE COMPUWARE PROPRIETARY *
//* DATA ACCESS METHOD (DDIO) FILES. (SEQUENTIAL) *
//* *
//* *** THIS JCL CAN BE USED TO ALLOCATE ALL SUPPORTED SEQ. *** *
//* *** DDIO FILE TYPES *** *
//* *
//* NOTE: SECONDARY EXTENTS MUST NOT BE USED. *
//* *
//**********************************************************************
//* CREATE SEQUENTIAL REPORT, SOURCE LISTING, AND OTHER *
//* DDIO FILES. *
//**********************************************************************
//*
//CXALLDS PROC VOLSER=VVVVVV, <--- SUPPLY VOLSER
// CXDDIO='COMPWARE.CX.DDIO', <--- CHECK DSN
// BLKSIZE=27998, <--- BLKSIZE
// BLKNO=4500, <--- NUMBER OF BLKS
// DUNIT='SYSDA' <--- DASD UNIT
//*
//STEP01 EXEC PGM=IEFBR14
//CXDDIO DD DSN=&CXDDIO,
// DISP=(,CATLG),
// UNIT=&DUNIT,
// SPACE=(&BLKSIZE,(&BLKNO)),
// VOL=SER=&VOLSER
// PEND
//JCLALLOC EXEC CXALLDS |
|
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi Robert,
I created the DDIO file using your JCL, but when I compile with xped 'y' in changeman the job is failing with the following error. pls advise.
PCOPTN028-I COMPUWARE COBOL PROCESSOR - RELEASE 08.06.00 (PTF CXN0139)
PCOPTN027-I COBOL(OUTPUT(NOPRINT, NODDIO))
PCOPTN027-I DDIO(OUTPUT(FIND))
PCOPTN027-I LANGPARM(XREF, MAP)
PCOPTN027-I LANGUAGE(COBOL/370)
PCOPTN027-I PRINT(OUTPUT(LIST, XREF, MAP))
PCOPTN027-I PROCESSOR(OUTPUT(PRINT, DDIO))
PCOPTN027-I AWO, NOC(E), LIB, MAP, BUF(128K), CP(37), DATA(31), OFF, VBREF, X
PCOPTN271-S CWPDDIO IS NOT A SOURCE DDIO FILE OR DATABASE.
PCFLEX095-W
PCFLEX095-W "BUFSIZE" VALUE DECREASED BECAUSE IT EXCEEDED DATA MANAGEMENT MAX
PCFLEX095-W
PCOPTN041-I PROCESSED ON 11/05/2009 AT 05:00:21 |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
Quote: |
PCOPTN271-S CWPDDIO IS NOT A SOURCE DDIO FILE OR DATABASE. |
I think you will find that the qsam that you created
does not support xpeditor use of a ddio file while debugging.
the qsam file is probably only a methodology to move, print members.
I believe that you will have to create a VSAM DDIO file,
which I did not see until the 8 or 10th post.
and was not sure if a new release of xpeditor supported the qsam for debugging.
the error code that you received indicates that qsam is not what you need. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi Dick,
Can I use the same JCL to create the VSAM file using IDCAMS something like that... |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
again,
go back to the utilities option of the ISPF xpeditor screens,
and use the screen to generate jcl to create a job that creates a vsam ddio file. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
Whether the DDIO is VSAM or sequential, this message
Quote: |
PCOPTN271-S CWPDDIO IS NOT A SOURCE DDIO FILE OR DATABASE. |
tells me you need to contact your site support group for assistance. Compuware has started linking DDIO files into a report and source database, and the message implies that your file needs to be so linked. The procedure to do this will be known to your site support group and the database may well have restricted access that would prevent you from doing this on your own. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Thanks Robert and Dick for your continued support. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi All,
I have created a shared Directory DDIO file and when i run the job I am getting following error..
Code: |
PCOPTN041-I DDIO
PCOPTN041-I OUTPUT ( NOLIST, NOPMAP, NOOFFSET, NOCLIST, NOXREF, NODMAP, NOMAP
PCOPTN041-I ( PROGRAM-NAME( ) )
PCOPTN041-I
PCOPTN041-I PRINT
PCOPTN041-I OUTPUT ( SOURCE, LIST, PMAP, OFFSET, CLIST, XREF, DMAP, MAP )
PCOPTN041-I
PCSIO 054-S NO DATABASE FILES IN SELECTION LIST .
PCSIO 006-S OUTPUT FILE CWPDDIO OPENMEM ERROR, RETURN CODE=48-046.
PCDRVR053-I ** ERRORS PROCESSING LISTING CS001478 DATED 11/06/2009 AT 08:57:4 |
This my DDIO info. Pls advise..
Code: |
SHARED DIRECTORY INFORMATION
AM(ACCESS METHOD) ............... VSAM
BLKSIZE ......................... 18425
OTHER INFORMATION
DIRECTORY FORMATTED BY DDIO ... 8.6.0
REQUIRES MINIMUM DDIO RELEASE . 7.0.0
TOTAL BLOCKS IN SHARED DIR .... 200
USED BLOCKS ................... 19(10%)
NUMBER OF EXTENTS ............. 1
DBMODEL INFORMATION:
DBMODEL ........................ NOT FOUND OR HAS NOT BEEN DEFINED
NUMBER OF ATTACHED DATABASE(S)................ 0 |
|
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
It does not appear your DDIO is defined correctly. See the Compuware manual Enterprise Common Components User/Reference Guide MVS for details on setting up a DBMODEL. It's been quite a while since I've had to set up any of this, so my memory does not recall the exact steps. I think the process was to allocate the DDIO, format it using the utility, and then link it to a database. But it's fuzzy so I could be forgetting a step or two.
If you have not contacted your site support group, I strongly recommend you do so since some of the Compuware definitions depend upon what is already defined at your site. |
|
Back to top |
|
|
ibmmainframe1
New User
Joined: 26 Jul 2005 Posts: 64 Location: India
|
|
|
|
Hi All,
I created DDIO using someone's else in Fileaid.
All these days I was trying to allocate new file or xped to create and that was failing.
Today in Fileaid utilities copy option used to copy someone's into mine and it worked.
Thanks all for your help. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Good to hear it is working - thank you for the update
d |
|
Back to top |
|
|
David Ashlock
New User
Joined: 02 Nov 2011 Posts: 2 Location: USA
|
|
|
|
Our experience with the PCOPTN271-S CWPDDIO IS NOT A SOURCE DDIO FILE OR DATABASE. was due to a security issue and not based on the definition of the file. The user did not have UPDATE CONTROL or ALL and was not allowed to write to dataset. |
|
Back to top |
|
|
Gary McDowell
Active User
Joined: 15 Oct 2012 Posts: 139 Location: USA
|
|
|
|
David Ashlock wrote: |
Our experience with the PCOPTN271-S CWPDDIO IS NOT A SOURCE DDIO FILE OR DATABASE. was due to a security issue and not based on the definition of the file. The user did not have UPDATE CONTROL or ALL and was not allowed to write to dataset. |
Welcome David.
As an FYI the original post of this thread was Tue Nov 03, 2009 1:00 pm. |
|
Back to top |
|
|
David Ashlock
New User
Joined: 02 Nov 2011 Posts: 2 Location: USA
|
|
|
|
I know, but I just came across this issue for us and that was our issue, same message, different problem. |
|
Back to top |
|
|
|