IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Trying to define a VSAM dataset with large length.


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
genesis786

Active User


Joined: 28 Sep 2005
Posts: 210
Location: St Katherine's Dock London

PostPosted: Mon Jun 25, 2012 2:53 pm
Reply with quote

[Sorry, by mistake i somehow posted in a wrong forum]
Hi I am trying to define a VSAM KSDS data set with very long length (32004) for simulating a scenario via CICS. I only require one record in the file.

I am using following code

Code:

  DELETE XXXXX.TEST1.VSAM CLUSTER PURGE       
  IF MAXCC LE 08 THEN SET MAXCC = 0               
  DEFINE CLUSTER ( -                             
           NAME(XXXXX.TEST1.VSAM) -           
           TRACKS(1000,1) -                       
           CISZ(32768) -                         
           RECORDSIZE(1,32004) -                 
           FREESPACE(0,0) -                       
           KEYS(10,0) -                           
           INDEXED -                             
           ) -                                   
         DATA    ( -                             
           NAME (XXXXX.TEST1.VSAM.D)) -       
         INDEX   ( -                             
           NAME (XXXXX.TEST1.VSAM.I) -       
           CISZ(32768) )                         
/*                                               


after executing i received the following error

Code:

RETURN CODE IS 212 REASON CODE IS 4 IGG0CLEQ                           
IGD306I UNEXPECTED ERROR DURING IGG0CLEQ PROCESSING                     
RETURN CODE 212 REASON CODE 4                                           
THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU                         
SMS MODULE TRACE BACK - VTSCU VTSCT VTSCH VTSCG VTSCD VTSCC VTSCR SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00351                         
IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET                         
XXXXX.TEST1.VSAM                                                   
IDC3014I CATALOG ERROR                                                 


i looked at the possible explanation of the error in the forum and made the changes to CISZ to 32768 and kept the record size to 32004. Even after adjusting the CISZ, still I am getting the same error. Could anyone please share some ideas?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA

PostPosted: Mon Jun 25, 2012 6:16 pm
Reply with quote

1. Change TRACKS to CYL -- the root cause of your problem is that the system doesn't like the 32K CISIZE with allocation in tracks.
2. Try adding a VOLUME parameter -- it is not optional.
3. If your key length is 10, why are you telling the system that the average record length is 1?
4. If the file is going to have 1 record, why allocate 1000 tracks?
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Mon Jun 25, 2012 6:17 pm
Reply with quote

RECORDSIZE(1,32004) -

KEYS(10,0) -
Back to top
View user's profile Send private message
Pete Wilson

Active Member


Joined: 31 Dec 2009
Posts: 582
Location: London

PostPosted: Tue Jun 26, 2012 3:06 pm
Reply with quote

The error looks more like an allocation issue related to the wrong dataset name or something. Try just creating a flat-file as a test using the same hlq and see what happens.

I'd also suggest you remove CYL or TRK size specification and replace with the RECORDS parameter. IDCAMS will figure out the appropriate allocation size based on that. VOLUMES specification shouldn't be necessary if it's SMS managed. RECORDSIZE should have minimum and maximum of the same values as it is only one record so there are no variations in record length. CISIZE can be ommitted as again, IDCAMS will select the appropriate Data CISIZE based on the RECORDSIZE, and Index CISIZE based on KEYS. You may need to check that there is a CICS buffer pool for 32k records.

RECORDSIZE(32004,32004) -
RECORDS(1) -
KEYS(10,0) -
Back to top
View user's profile Send private message
genesis786

Active User


Joined: 28 Sep 2005
Posts: 210
Location: St Katherine's Dock London

PostPosted: Wed Jun 27, 2012 1:52 pm
Reply with quote

Robert Sample wrote:
1. Change TRACKS to CYL -- the root cause of your problem is that the system doesn't like the 32K CISIZE with allocation in tracks.
2. Try adding a VOLUME parameter -- it is not optional.
3. If your key length is 10, why are you telling the system that the average record length is 1?
4. If the file is going to have 1 record, why allocate 1000 tracks?


icon_smile.gif thanks a lot.. simply changed TRK to CYL and it worked!!
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA

PostPosted: Wed Jun 27, 2012 4:46 pm
Reply with quote

Glad to hear it worked.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Store the data for fixed length COBOL Programming 1
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts PARSE Syntax for not fix length word ... JCL & VSAM 7
No new posts Access to non cataloged VSAM file JCL & VSAM 18
No new posts FINDREP - Only first record from give... DFSORT/ICETOOL 3
Search our Forums:

Back to Top