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

GDG Error: POSITIONAL PARM MUST BE SPECIFIED BEFORE KEYWORD


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

New User


Joined: 17 Feb 2007
Posts: 46
Location: mumbai

PostPosted: Fri Mar 16, 2007 5:08 pm
Reply with quote

Hi All

I am getting an error while writing a GDG program please give me solution to solve it.

Code:
               
//STEP1 EXEC PGM=IDCAMS                                       
//SYSIN  DD     *                                             
    DEFINE GDG( -                                             
               NAME(OSOP.BCB1O.TEST)-                         
               LIMIT(10)-                                     
               NOEMPTY -                                     
               SCRATCH)                                       
//STEP2  EXEC PGM=IEFBR14                                     
//SYSPRINT DD SYSOUT=*                                       
//MODEL1 DD DSN=OSOP.BCB1O.TEST,DISP=(NEW,CATLG,DELETE),     
//            UNIT=3390,VOL=SER=WORKY1,                       
//            SPACE(TRK,0),                                   
//            DCB=(LRECL=80,RECFM=FB,BLKSIZE=800)             
//                                                           


JESYSMSG

 STMT NO. MESSAGE                                                               
        6 IEFC006I POSITIONAL PARAMETERS MUST BE SPECIFIED BEFORE KEYWORD PARAMETER

JESJCL


1 //MYJOB JOB 'BHAVESH',NOTIFY=&SYSUID                       
  IEFC653I SUBSTITUTION JCL - 'BHAVESH',NOTIFY=BCB1O         
2 //STEP1 EXEC PGM=IDCAMS                                   
3 //SYSIN  DD     *                                         
4 //STEP2  EXEC PGM=IEFBR14                                 
5 //SYSPRINT DD SYSOUT=*                                     
6 //MODEL1 DD DSN=OSOP.BCB1O.TEST,DISP=(NEW,CATLG,DELETE),   
  //            UNIT=3390,VOL=SER=WORKY1,                   
  //            SPACE(TRK,0),                               
  //            DCB=(LRECL=80,RECFM=FB,BLKSIZE=800)         


Can any one explain me the error and give me a proper solution
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Fri Mar 16, 2007 5:12 pm
Reply with quote

It is seeing your SPACE as a positional parameter since it does not have the keyword required "="........
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Mar 16, 2007 5:26 pm
Reply with quote

What your JCL is trying to do is to create a dataset with exactly the same name as your GDG base. Perhaps specifying (+1) might help.

I guess from the DD name of MODEL your are attempting to set up a model DSCB or reference DSCB to use in conjunction with the GDG base.

If your site has SMS installed, forget about having a model or reference DSCB, you do not need it.

Go chat with your nice storage guys and say to them, please set up a DUMMY DATACLAS that will be attributed to every GDG that is created either tape or DASD, SMS or NON SMS. The DATACLAS should NOT allocate any attributes to the GDG being created i.e. RECFM, LRECL, or anything else, hence a dummy DATACLAS. These attributes should be taken from the JCL.

This way you do not need any models or dummy dcbs, no problems for ANY GDG, as above - SMS, NON SMS, tape or DASD.
Back to top
View user's profile Send private message
ybhavesh
Warnings : 1

New User


Joined: 17 Feb 2007
Posts: 46
Location: mumbai

PostPosted: Fri Mar 16, 2007 5:31 pm
Reply with quote

Hi i am getting error again maxcc=16

//MYJOB JOB 'BHAVESH',NOTIFY=&SYSUID
//STEP1 EXEC PGM=IDCAMS
//SYSIN DD *
DEFINE GDG( -
NAME(OSOP.BCB1O.TEST)-
LIMIT(10)-
NOEMPTY -
SCRATCH)
//STEP2 EXEC PGM=IEFBR14
//SYSPRINT DD SYSOUT=*
//MODEL1 DD DSN=OSOP.BCB1O.TEST,DISP=(NEW,CATLG,DELETE),
// UNIT=3390,VOL=SER=WORKY1,
// SPACE=(TRK,0),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=800)
//


JESYSMSG

ICH70001I BCB1O LAST ACCESS AT 17:20:54 ON FRIDAY, MARCH 16, 2007
IEF236I ALLOC. FOR MYJOB STEP1
IEF237I JES2 ALLOCATED TO SYSIN
IDC4999I UABORT CODE 36
IEC130I AMSDUMP DD STATEMENT MISSING
IEF142I MYJOB STEP1 - STEP WAS EXECUTED - COND CODE 0016
IEF285I BCB1O.MYJOB.JOB00027.D0000101.? SYSIN
IEF373I STEP/STEP1 /START 2007075.1722
IEF374I STEP/STEP1 /STOP 2007075.1722 CPU 0MIN 00.01SEC SRB 0MIN 00.00
IEF236I ALLOC. FOR MYJOB STEP2
IEF237I JES2 ALLOCATED TO SYSPRINT
IGD100I 0813 ALLOCATED TO DDNAME MODEL1 DATACLAS ( )
IEF142I MYJOB STEP2 - STEP WAS EXECUTED - COND CODE 0000
IEF285I BCB1O.MYJOB.JOB00027.D0000102.? SYSOUT
IEF285I OSOP.BCB1O.TEST CATALOGED
IEF285I VOL SER NOS= WORKY1.
STEP/STEP2 /START 2007075.1722
STEP/STEP2 /STOP 2007075.1722 CPU 0MIN 00.01SEC SRB
JOB/MYJOB /START 2007075.1722
JOB/MYJOB /STOP 2007075.1722 CPU 0MIN 00.02SEC SRB
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Fri Mar 16, 2007 5:39 pm
Reply with quote

Where is the output from the IDCAMS? That will tell you why you got an RC16.
For step2 to work correctly, you will have to delete the existing occurances of OSOP.BCB1O.TEST and add the "(+1)" to the DSN=.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Mar 16, 2007 5:54 pm
Reply with quote

Mmmmmmmmmmmmmmmmm
Code:

//STEP1 EXEC PGM=IDCAMS                                       
//SYSIN  DD     *                                             
    DEFINE GDG( -                                             
               NAME(OSOP.BCB1O.TEST)-                         
               LIMIT(10)-                                     
               NOEMPTY -                                     
               SCRATCH)                                       
//STEP2  EXEC PGM=IEFBR14                                     
//SYSPRINT DD SYSOUT=*               

Looks to me as if the SYSPRINT for IDCAMS has become misplaced and now lives with the IEFBR14 step, which has no need whatsoever for a SYSPRINT DD.

I suggest you put the SYSPRINT DD back where it belongs in the IDCAMS step. That way we'll get some usable error info.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Fri Mar 16, 2007 7:56 pm
Reply with quote

Hello,

If you are getting new errors, please post the modified jcl, control statements, and error message(s).
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 Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts JCL EXEC PARM data in C Java & MQSeries 2
No new posts Need to specify PARM='POSIX(ON) Java & MQSeries 4
Search our Forums:

Back to Top