Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

IMPLEMENTOR DEFINED CONDITION

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Mon Mar 16, 2009 2:38 pm    Post subject: IMPLEMENTOR DEFINED CONDITION
Reply with quote

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
View user's profile Send private message

dick scherrer

Site Director


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

PostPosted: Mon Mar 16, 2009 2:51 pm    Post subject:
Reply with quote

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
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Mon Mar 16, 2009 2:56 pm    Post subject: Reply to: IMPLEMENTOR DEFINED CONDITION
Reply with quote

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
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Mon Mar 16, 2009 2:58 pm    Post subject:
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Mon Mar 16, 2009 3:02 pm    Post subject:
Reply with quote

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
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Mon Mar 16, 2009 3:02 pm    Post subject:
Reply with quote

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
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10203
Location: italy

PostPosted: Mon Mar 16, 2009 3:03 pm    Post subject: Reply to: IMPLEMENTOR DEFINED CONDITION
Reply with quote

repeat on

the wording IMPLEMENTOR DEFINED CONDITION and the whole message
are not standard IBM wording/message, check with Your support
Back to top
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Mon Mar 16, 2009 4:51 pm    Post subject: Invalid block size unable to open Dataset
Reply with quote

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
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Mon Mar 16, 2009 5:37 pm    Post subject:
Reply with quote

Has anybody encounter the issue like this before?
Back to top
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Mon Mar 16, 2009 8:43 pm    Post subject:
Reply with quote

Hello,

So, is this now resolved?
Back to top
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Tue Mar 17, 2009 9:13 am    Post subject:
Reply with quote

Nop icon_sad.gif

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
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Tue Mar 17, 2009 9:28 am    Post subject:
Reply with quote

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
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Tue Mar 17, 2009 9:42 am    Post subject:
Reply with quote

Thanks a lot Dick.

Now it does make sense.. icon_biggrin.gif
Back to top
View user's profile Send private message
dick scherrer

Site Director


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

PostPosted: Tue Mar 17, 2009 9:51 am    Post subject: Reply to: IMPLEMENTOR DEFINED CONDITION
Reply with quote

You're welcome icon_smile.gif

d
Back to top
View user's profile Send private message
himanshu7

Active User


Joined: 28 Aug 2007
Posts: 131
Location: At Desk

PostPosted: Tue Mar 17, 2009 10:31 am    Post subject:
Reply with quote

We can avoid this error when we specify the BLKSIZE with the same utility IEFBR14.Why?
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Tue Mar 17, 2009 2:46 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Tue Mar 17, 2009 2:49 pm    Post subject:
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. How to pass the previous month date i... Suganya87 DFSORT/ICETOOL 5 Mon Oct 31, 2016 4:13 pm
No new posts Getting list of tables defined under ... kishpra DB2 2 Wed Aug 24, 2016 10:36 am
No new posts INCLUDE condition questions van bui DFSORT/ICETOOL 1 Thu Jun 30, 2016 9:52 am
No new posts 2 vsam file compare and update a fiel... ABINAYATHULASI DFSORT/ICETOOL 6 Sun May 29, 2016 11:15 am
No new posts Update the Sortout file with record c... karthik_sripal SYNCSORT 8 Tue May 17, 2016 8:52 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us