View previous topic :: View next topic
|
Author |
Message |
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Hi All
1.Through the 1st step am deleting the Dataset if it is existing
2.Step 2nd is creating the same Dataset again with its DCB parameter,
however i have not coded the Blksize, letting system to give the values.
3. The job went fine.
But when i tried opening the file 'DATASET1' got an error "Invalid block size"
Code: |
//STEP0010 EXEC PGM=IEFBR14,COND=(0,NE)
//MMWT DD DSN=DATASET1,
// DISP=(MOD,DELETE,DELETE),
// UNIT=SYSDA,SPACE=(TRK,0)
//STEP0020 EXEC PGM=IEFBR14,COND=(0,NE)
//MMWT DD DSN=DATASET1,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(1,5),RLSE),
// DCB=(RECFM=FB,LRECL=920) |
Posting the DSN information
Code: |
*************************************************************************
Command ===>
More:
Data Set Name . . . . : TGCVPG0.MBS1.V817.MMWT.SE
General Data Current Allocation
Management class . . : MCSTAND Allocated cylinders : 1
Storage class . . . : SCSTAND Allocated extents . : 1
Volume serial . . . : TGC103
Device type . . . . : 3390
Data class . . . . . : **None** Current Utilization
Organization . . . : NONE Used cylinders . . : 0
Record format . . . : FB Used extents . . . : 0
Record length . . . : 350
Block size . . . . : 0
1st extent cylinders: 1
Secondary cylinders : 5
Data set name type :
Creation date . . . : 2009/03/13 Referenced date . . : 2009/03/14
Expiration date . . : ***None***
************************************************************************** |
Am able to create and open the same Dataset, when created with TSO option with blksize=0
Because of the above issue my JCL is abending with an error-->
Code: |
+*********************************************************
+SMMWT REQ=01 STA=90 RC=000000 LOC=O1WT MSG=MBD000 - OPEN- OPEN ERROR - MMWT
+IMPLEMENTOR DEFINED CONDITION |
Could you guys help in resolving the issue? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
The jcl you ran only allocated space - it did not build a proper dataset.
Using iebgener or your sort product, copy a dummy input to the new output file. Then you should be able to use it. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
I wish that people posting would learn to post consistent information
how do you expect to get help when You post...
the jcl about something called
dataset1 with a record length of 920
the ISPF info about something called
TGCVPG0.MBS1.V817.MMWT.SE with a record length of 350
also the wording IMPLEMENTOR DEFINED CONDITION and the whole message
are not standard IBM wording/message, check with Your support |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
The Above JCL is just an example, But im using Cobol pgm and then trying to create the new DSN and that is throwing the error
"IMPLEMENTOR DEFINED CONDITION '"
But if the same file if i have created with some block size it is running fine. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
As explained earlier, the way you built the dataset in jcl was incorrect. . .
BLKSIZE=0 is sometimes a problem when only jcl allocates a dataset. Using iebgener or the sort should work. |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Sorry for that
Posting the DSN information
*************************************************************************
Command ===>
More:
Data Set Name . . . . : DATASET1
General Data Current Allocation
Management class . . : MCSTAND Allocated cylinders : 1
Storage class . . . : SCSTAND Allocated extents . : 1
Volume serial . . . : TGC103
Device type . . . . : 3390
Data class . . . . . : **None** Current Utilization
Organization . . . : NONE Used cylinders . . : 0
Record format . . . : FB Used extents . . . : 0
Record length . . . : 920
Block size . . . . : 0
1st extent cylinders: 1
Secondary cylinders : 5
Data set name type :
Creation date . . . : 2009/03/13 Referenced date . . : 2009/03/14
Expiration date . . : ***None***
************************************************************************** |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
repeat on
the wording IMPLEMENTOR DEFINED CONDITION and the whole message
are not standard IBM wording/message, check with Your support |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Hi Dick,
Now the issue which im encountring is(for example plz refer the above post) in step one im trying to delete the DSN of the previous run and then in step two i want to updated the same file through one of my functional cobol pgm, so in the second step im recreating the DSN with parameter as below ---->
//MMWT DD DSN=DATASET1,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(1,5),RLSE),
// DCB=(RECFM=FB,LRECL=920)
This particular DSN should be created and updated with many other i/p files as per the requirement.
But i believe as the BLKSIZE is not mentioned the file is not opening and due to which we are facing File status as 90.
We are able to resolve the same issue if we have created the file outside the JCL i.e TSO with or without mentioning the BLKsize as the system will take the blksize by itself also adding one dummy rec and skipping the step of creating this file in JCL. |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Has anybody encounter the issue like this before? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
So, is this now resolved? |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Nop
However this concept has raised one more question and i.e. Can anybody also explain the entire concept of creating the file through IEBGENER and SORT and why we are adding one dummy record to it? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
Can anybody also explain the entire concept of creating the file through IEBGENER and SORT |
Using these programs cause the output file to actually be opened and a "real" end-of-file written. Using IEFBR14 does not open any files, so there is no eof written. As i mentoned earlier, only space is allocated.
Quote: |
why we are adding one dummy record to it |
Copying from a dd dummy dataset does not copy a dummy record. There are no records in a dd dummy dataset, so the copy goes to end on the first read. All that is done is that the file is opened as output and the eof is written when the file is closed.
Something that will most likely be more confusing is that if the data is sms-managed, this is not a problem. Suggest you talk with your storage management people for details. |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
Thanks a lot Dick.
Now it does make sense.. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
You're welcome
d |
|
Back to top |
|
|
himanshu7
Active User
Joined: 28 Aug 2007 Posts: 131 Location: At Desk
|
|
|
|
We can avoid this error when we specify the BLKSIZE with the same utility IEFBR14.Why? |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
himanshu7 wrote: |
We can avoid this error when we specify the BLKSIZE with the same utility IEFBR14.Why? |
What value do you code for BLKSIZE? Not sure if you missed this from an earlier post from Dick
Quote: |
Using IEFBR14 does not open any files, so there is no eof written. As i mentoned earlier, only space is allocated. |
|
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Hi,
Quote: |
What value do you code for BLKSIZE? |
If it was BLKSIZE=0, it can often cause problems if the dataset is not opened and closed unless your SMS environment has been correctly established.
If it has not, then the BLKSIZE=0 will be honoured and the dataset will have that attribute, which makes the dataset invalid for processing by DFHSM, or whatever other ILM software you use.
The correct coding is RECFM=xx,LRECL=yyy. |
|
Back to top |
|
|
|