creating a vsam file using jcl

Question

I am trying to create a VSAM file using IDCAMS utility in JCL. MAXCC code that it returns is 0000.

But the newly created vsam file is not displayed in the list when I try to list it using 3.4.

Can anyone help me on this.?

The code that I have used is :

//VSAM0001 JOB (ACCT),CLASS=A,MSGLEVEL=(1,1
//             NOTIFY=&SYSUID,MSGCLASS=A   
//STEP0001 EXEC PGM=IDCAMS                 
//SYSPRINT DD  SYSOUT=*                    
//SYSIN    DD  *                           
    DEFINE CLUSTER -                       
       (NAME(DOMAIN.MYFILE.MYVSAM) -   
       VOL(AGH419) -                   
       KEYS(16 0) -                    
       RECORDSIZE(120 120) -           
       INDEXED -                       
       REUSE ) -                       
    DATA -                                 
      (NAME(DOMAIN.MYFILE.MYVSAM.DATA) - 
      CISZ(8192) -                      
      RECORDSIZE(120 120) -             
      FSPC(0 0) ) -                     
    INDEX -                                
      (NAME(DOMAIN.MYFILE.MYVSAM.INDEX) )
/*

It would help to give us the instructions you used. Otherwise, I could only guess, which is not a good problem-solving exercise. — bmakos, Nov 24 '14 at 12:09
Please show your IDCAMS control statements and any messages displayed in SYSPRINT or JESMSGLG when you run your job. — cschneid, Nov 24 '14 at 12:41
The message displayed in SYSPRINT is: INCORRECT SPECIFICATION OF SPACE ALLOCATION — Kinjal Shah, Nov 25 '14 at 06:12
The message ID is always important. Always include it. Try poking the message reference into IBM's LookAt web service and seeing what it says. — Bill Woodger, Nov 25 '14 at 07:22
Thank you all for the response. IBM's LookAt utility helped. I have not specified the CYL parameter which is required because of which I have got the INCORRECT SPECIFICATION OF SPACE ALLOCATION.Now it is working. — Kinjal Shah, Nov 25 '14 at 07:47
Always try to copy some control cards which already work. It'll save problems like this. When you get an error message, look it up. There are lots of Messages and Codes manuals, so IBM's LookAt is very useful as it finds the correct manual for you and extracts the message. Don't try that with COBOL, though. COBOL error messages are self-explanatory. — Bill Woodger, Nov 25 '14 at 10:19
@KinjalShah can you put your findings as an answer and mark it as accepted? — dsolimano, Dec 17 '14 at 15:38
While creating the VSAM file using IDCAMS utility in JCL, you need to supply the disk storage paraeters. — Kinjal Shah, Dec 18 '14 at 08:50

score 3 · Answer 1 · edited Oct 23 '19 at 21:44

3

While creating VSAM file using IDCAMS utility, you need to specify all the storage parameters that are required like CYL, TRK etc..If you miss out any of these parameters then JCL won't be able to know where to store the newly created VSAM. So, in DEFINE portion of your JCL file, supply all the necessary storage parameters and you are good to go. :) Hope this helps.!

edited Oct 23 '19 at 21:44

mjsqu

5,151
1
17
21

answered Feb 10 '15 at 06:46

Kinjal Shah

31
1
8

score 1 · Answer 2 · answered Jan 21 '15 at 14:24

As the author wrote in the comments:

Thank you all for the response. IBM's LookAt utility helped. I have not specified the CYL parameter which is required because of which I have got the INCORRECT SPECIFICATION OF SPACE ALLOCATION.Now it is working. – Kinjal Shah

score 0 · Answer 3 · answered Dec 24 '14 at 20:51

0

All messages will have an id (e.g., IEA1235) that can be used when searching for what generated the message.

You need to specify space in your IDCAMS 'DEFINE'. Look in your manual (or online) for specifying space for VSAM clusters.

answered Dec 24 '14 at 20:51

Dave Nagy

21
7

creating a vsam file using jcl

3 Answers3