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

IAM File Dynamic Allocation Failing


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

New User


Joined: 03 Apr 2010
Posts: 5
Location: India

PostPosted: Thu Oct 17, 2013 1:08 pm
Reply with quote

Hello!

IDCAMS IAM file allocation is failing frequently.

The issue is happening only for IAM files and not VSAM. We have raised with Bank’s IBM support team as well. They recommend to change the define card volume allocation parameters.

But that doesn’t seem to be the problem. Please refer the SYSPRINT snippet below. Here,

1.Two files are being defined in a single IDCMAS step
a.HTLM2 is IAM with volume parameters CYL (1000 500) & 2 stars
b.HTLN2 is VSAM with volume parameters CYL (2000 500) & 2 stars
2.Allocation is failing for HTLM2 but passing for HTLN2 despite the fact that HTLN2 has higher space requirements

Not sure if changes to define card parameters will fix the issue. It seems that SMS is not reacting the same way for both IAM & VSAM.

Please help

Code:
1IDCAMS  SYSTEM SERVICES                                           TIME: 01:47:10        10/16/13     PAGE      1
0
  DELETE                                                         -
                VPP1.CMS.VSO.HTLM2                          -
                 PURGE                                           -
                 CLUSTER
0IDC3012I ENTRY VPP1.CMS.VSO.HTLM2 NOT FOUND
 IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLA3-42
 IDC0551I ** ENTRY VPP1.CMS.VSO.HTLM2 NOT DELETED
0IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
0
  DELETE                                                         -
                VPP1.CMS.VSO.HTLN2                          -
                 PURGE                                           -
                 CLUSTER
0IDC0550I ENTRY (D) VPP1.CMS.VSO.HTLN2.D DELETED
0IDC0550I ENTRY (I) VPP1.CMS.VSO.HTLN2.I DELETED
0IDC0550I ENTRY (C) VPP1.CMS.VSO.HTLN2 DELETED
0IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
0IKJ56893I DATA SET VPP1.CMS.VSO.HTLM2 NOT ALLOCATED+
 IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET
 VPP1.CMS.VSO.HTLM2
 IGD17277I THERE ARE (440) CANDIDATE VOLUMES OF WHICH (440) ARE ENABLED OR QUIESCED
 IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1
 WERE ELIGIBLE FOR VOLUME SELECTION.
 THE CANDIDATE STORAGE GROUPS WERE:VPCMSSG
 IGD17279I 438 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ON THE INCLUDE LIST
 IGD17279I 1 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT SPACE (041A041D)
 IAMW60 IAM DYNALLOC   FAILED  SMS FAILED REQUEST, REFER TO PRIOR MESSAGE(S)
 IAMW61 IAM DYNALLOC   FAILED  CODE=970C INFO=0000      CLUSTER=VPP1.CMS.VSO.HTLM2
0
   IF MAXCC < 12 THEN SET MAXCC=0

  DEFINE CLUSTER                                                 -
        ( NAME(VPP1.CMS.VSO.HTLM2)                          -
        FREESPACE(0 0)                                           -
        OWNER($IAM)                                              -
        INDEXED                                                  -
        KEYS(44,0)                                               -
        REUSE                                                    -
        RECORDSIZE(6000,6000)                                    -
        SHAREOPTIONS(2,3)                                        -
        SPEED                                                    -
        VOLUME(* *) )                                            -
    DATA                                                         -
        ( NAME(VPP1.CMS.VSO.HTLM2.D)                       -
        CONTROLINTERVALSIZE(6144)                                -
        CYLINDERS (1000 500) )                                   -
    INDEX                                                        -
        ( NAME(VPP1.CMS.VSO.HTLM2.I)     )
0IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
 VPP1.CMS.VSO.HTLM2
 RETURN CODE IS 16 REASON CODE IS 0 IGG0CLIM
 IGD306I UNEXPECTED ERROR DURING IGG0CLIM PROCESSING
 RETURN CODE 16 REASON CODE 0
1IDCAMS  SYSTEM SERVICES                                           TIME: 01:47:10        10/16/13     PAGE      2
0THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU
 SMS MODULE TRACE BACK - VTSCU VTSCT VTSCH VTSCG VTSCD VTSCC VTSCR VTSUC
 SSIP4
 SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00015
 IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET
 VPP1.CMS.VSO.HTLM2
0IDC3014I CATALOG ERROR
 IDC3009I ** VSAM CATALOG RETURN CODE IS 16 - REASON CODE IS IGG0CLIM-0
0IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
0
  DEFINE CLUSTER                                                 -
        ( NAME(VPP1.CMS.VSO.HTLN2)                          -
        FREESPACE(20 25)                                         -
        INDEXED                                                  -
        KEYS(44,0)                                               -
        REUSE                                                    -
        RECORDSIZE(6000,6000)                                    -
        SHAREOPTIONS(2,3)                                        -
        SPEED                                                    -
        VOLUME(* *) )                                            -
    DATA                                                         -
        ( NAME(VPP1.CMS.VSO.HTLN2.D)                       -
        CONTROLINTERVALSIZE(8192)                                -
        CYLINDERS (2000 500) )                                   -
    INDEX                                                        -
        ( NAME(VPP1.CMS.VSO.HTLN2.I)     )
0IGD17070I DATA SET VPP1.CMS.VSO.HTLN2
 ALLOCATED SUCCESSFULLY WITH 1 STRIPE(S).
 IGD17172I DATA SET VPP1.CMS.VSO.HTLN2
 IS ELIGIBLE FOR EXTENDED ADDRESSABILITY
0IDC0508I DATA ALLOCATION STATUS FOR VOLUME VCM166 IS 0
0IDC0508I DATA ALLOCATION STATUS FOR VOLUME VCM317 IS 0
0IDC0509I INDEX ALLOCATION STATUS FOR VOLUME VCM166 IS 0
0IDC0509I INDEX ALLOCATION STATUS FOR VOLUME VCM317 IS 0
 IDC0181I STORAGECLASS USED IS VPCMSSC
 IDC0181I DATACLASS USED IS VPEXTDC
0IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
0
0IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Thu Oct 17, 2013 1:49 pm
Reply with quote

Talk to your technical people responsible for IAM. ( * * ) may not be what you should be doing.
Back to top
View user's profile Send private message
vj.kbay

New User


Joined: 03 Apr 2010
Posts: 5
Location: India

PostPosted: Thu Oct 17, 2013 2:16 pm
Reply with quote

Hi Bill,

New DATACLAS defintions or changes to existing ones are not in our control. And for various reasons it is tough to get these changes done.

IAM manual says,

Quote:
When an IAM file is defined with a Storage Class that specifies Guaranteed Space, the primary allocation quantity is allocated on each volume at DEFINE time, as per the SMS non-VSAM rules. When Guaranteed Space is NOT specified, only the first volume is selected at DEFINE, and the subsequent volumes are cataloged as an '*'.


We are trying to find out from the IBM support group the 'guaranteed space' setup for non-VSAM files. Refer the following messages,

Code:
 IGD17279I 438 VOLUMES WERE REJECTED BECAUSE THEY WERE NOT ON THE INCLUDE LIST
 IGD17279I 1 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT SPACE (041A041D)


With our limitations, guess increasing the stars (*) and reducing the allocation should help provided current setting says that for non-VSAM Guaranteed Space is NOT specified.
Back to top
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1353
Location: Israel

PostPosted: Thu Oct 17, 2013 6:47 pm
Reply with quote

Maybe the OWNER($IAM) is the problem ?
It's the only difference between the two DEFINE CLUSTER (except the size)
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10873
Location: italy

PostPosted: Thu Oct 17, 2013 6:52 pm
Reply with quote

Code:
OWNER($IAM)

unfortunately that is the way to specify that a dataset is IAM managed icon_cool.gif

most probably the ACS routines are mangling the allocation stuff!
Back to top
View user's profile Send private message
vj.kbay

New User


Joined: 03 Apr 2010
Posts: 5
Location: India

PostPosted: Thu Oct 17, 2013 7:11 pm
Reply with quote

Enrico,

can you share some information on ACS routines.

Any hyperlinks or manuals which will provide some insight.

Rgds,
VJ
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10873
Location: italy

PostPosted: Thu Oct 17, 2013 7:33 pm
Reply with quote

see here
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2I670/CCONTENTS?SHELF=dgt2bkb1&DN=SC26-7407-07&DT=20110609125654
and here
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S2A1/CCONTENTS?SHELF=dgt2bkb1&DN=SC26-7402-16&DT=20120126150025
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 FTP VB File from Mainframe retaining ... JCL & VSAM 8
No new posts Extract the file name from another fi... DFSORT/ICETOOL 6
No new posts How to split large record length file... DFSORT/ICETOOL 10
No new posts Extracting Variable decimal numbers f... DFSORT/ICETOOL 17
No new posts SFTP Issue - destination file record ... All Other Mainframe Topics 2
Search our Forums:

Back to Top