Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Unable to write records to multivolume dataset using PUT

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> PL/I & Assembler
View previous topic :: :: View next topic  
Author Message
saravananj

New User


Joined: 23 Nov 2007
Posts: 17
Location: Chennai

PostPosted: Mon Jun 23, 2008 1:34 pm    Post subject: Unable to write records to multivolume dataset using PUT
Reply with quote

We have a production application which appends few records to a PS dataset. Since the dataset was becoming full, We recently changed the dataset properties. The new output dataset now resides on multiple volumes, previously it used to exist on a single volume.

The problem we are facing is the job completes successfully, but records are not being appended to the new multivolume dataset. I infact checked the return code after PUT got executed. The return code from PUT is zero. When I changed the dataset to a single volume dataset, the records are being appended.

Any pointers on why this is happening would be of great help for us. Here are DCB declarations of our output dataset

Quote:
AUDIT DCB DSORG=PS,MACRF=PM,DDNAME=JOURNAL1

The dataset properties are as follows,
Quote:
Organization . . . : PS
Record format . . . : FB
Record length . . . : 239
Block size . . . . : 27963
1st extent cylinders: 108
Secondary cylinders : 500

Thanks
Back to top
View user's profile Send private message

UmeySan

Active Member


Joined: 22 Aug 2006
Posts: 757
Location: Germany

PostPosted: Mon Jun 23, 2008 5:15 pm    Post subject:
Reply with quote

Pleasant morning Sir !

Times a go, i had nearly the same phenomena. We only altered the SMS-Parameters and had no look at the JCL. There was still the normal definition. DISP=(MOD)

We had to change this to DISP=(MOD,CATLG).

Even if the dataset is already catalog, this causes the entry of the new disks now used in the catalog.
Back to top
View user's profile Send private message
saravananj

New User


Joined: 23 Nov 2007
Posts: 17
Location: Chennai

PostPosted: Tue Jun 24, 2008 8:58 am    Post subject:
Reply with quote

UmeySan wrote:
Pleasant morning Sir !

Times a go, i had nearly the same phenomena. We only altered the SMS-Parameters and had no look at the JCL. There was still the normal definition. DISP=(MOD)

We had to change this to DISP=(MOD,CATLG).

Even if the dataset is already catalog, this causes the entry of the new disks now used in the catalog.


Thanks for the response. We are in fact using Dynalloc for the output dataset, I will check the SVC 99 settings and check with Storage guys and update the results.
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 -> PL/I & Assembler All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Inefficient BUILD - VB records paddin... Daniel Prosser SYNCSORT 6 Thu Dec 14, 2017 3:52 pm
No new posts ISSUE IN copying Sequential file reco... thesumitk JCL & VSAM 2 Wed Dec 13, 2017 3:07 pm
No new posts Unable to send mail with SMTP commands harsh.saxena579 JCL & VSAM 10 Tue Dec 12, 2017 1:58 pm
No new posts Looping REXX - unable to interrupt RAVISANKAR07 CLIST & REXX 3 Wed Dec 06, 2017 1:08 pm
No new posts Merging 2 records at multiple rows wi... Bijesh DFSORT/ICETOOL 2 Wed Dec 06, 2017 1:50 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us