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
 

 

Tformat or MFS problem?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IMS DB/DC
View previous topic :: :: View next topic  
Author Message
chowdhrykapildev

New User


Joined: 05 Aug 2009
Posts: 44
Location: Hyderabad

PostPosted: Tue Aug 11, 2009 5:05 pm    Post subject: Tformat or MFS problem?
Reply with quote

Hi all,

I had made few screen layout changes for 3 screens by adding new field to them. I had generated the new Tformats. I had moved them to the respective standard libraries (TLIB.TMYS.FORMAT). Every night an IMS job is run where the modules from TLIB.TMYS.FORMAT are copied into the IMS standard library. So, I can check the results of the changes only after the IMS job is run. The next day, when I gave the option of the screen which I had made the changes, after pressing enter got the below error message:

DFS057I REQUESTED BLOCK NOT AVAILABLE: 027FMYSSAA RC=04
0 0 -------------------------------------------------I134808

I had checked for the related above error msg in forum. I could find info on it but it didnt help me alot. Can anyone please help me out how to rectify the above error.

NOTE: I had tried testing by giving the below command.
/FORMAT MYSSAAF and got the same above error msg.

Waiting for your response.
Thanks in Advance.
Back to top
View user's profile Send private message

chowdhrykapildev

New User


Joined: 05 Aug 2009
Posts: 44
Location: Hyderabad

PostPosted: Tue Aug 11, 2009 5:08 pm    Post subject: Continuation of the above....
Reply with quote

I can also see that the related MYSSAAE, MYSSAAF Tformat modules are present in the IMS standard dataset library.
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 Aug 11, 2009 9:33 pm    Post subject:
Reply with quote

I don't do much IMSDC, however, about DFS057I, for RC=4, manuals says:
Quote:
DFS057I REQUESTED BLOCK NOT AVAILABLE: block name RC = reason code Explanation: MFS cannot fetch the control blocks required to process an output message or to process the /FORMATrequest. The block name in the message specifies the name of the block that could not be fetched and is either the MOD or the DOF name. If it is the DOF name, the first two bytes of the name are the device type and features printed in hexadecimal. For an interpretation of these two bytes, refer to "Format Library Member Selection" in IMS Version 7 Application Programming: Transaction Manager.

RC=04: The indicated block name was not found in the active format data set library. The following conditions can cause this reason code to be produced:

- There is a misspelled message output descriptor (MOD) name or the MOD does not exist in the active format data set library.

- A device output format (DOF) for the specified MOD with the device type and feature indicated does not exist in the active format data set library.
Back to top
View user's profile Send private message
Sandy Zimmer

Active Member


Joined: 13 Jun 2007
Posts: 826
Location: Wilmington, DE

PostPosted: Wed Aug 12, 2009 1:11 am    Post subject:
Reply with quote

I do not know your procedures. Is TLIB.TMYS.FORMAT the standard TEST MFS library? Is there more than 1 TEST MFS library? One more thing - you did change the cobol program for the increased message length - right?
Back to top
View user's profile Send private message
Sandy Zimmer

Active Member


Joined: 13 Jun 2007
Posts: 826
Location: Wilmington, DE

PostPosted: Wed Aug 12, 2009 8:27 pm    Post subject:
Reply with quote

One more thought - when you compiled your MFS, did it indicate a clean compile with the "CREATED" message?
Back to top
View user's profile Send private message
chowdhrykapildev

New User


Joined: 05 Aug 2009
Posts: 44
Location: Hyderabad

PostPosted: Wed Aug 12, 2009 10:54 pm    Post subject:
Reply with quote

Thanks Anuj, Sandy for the prompt reply.

The problem is solved now. I really apologize for delayed response.

@Sandy: TLIB.TMYS.FORMAT is the only Test MFS library which we have. I had even changed the Rules (PL1 pgms) to handle the new fields in the screens. I can also see the newly added field in the MFS load.

The problem was because of the device type 3270. In the job which creates Tformat, in one of the SDFSRESL loads, earlier I was trying to create Tformats using all the four device types 3270-A02, 3270-A03, 3270-A04, 3270-A07. Now, I had used the load which has only the device type 3270-A02. It worked fine. I can see the changes in the IMS screen now.

Thanks once again for all the quick replys. Do catch you soon again. :-)
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


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

PostPosted: Thu Aug 13, 2009 2:27 pm    Post subject:
Reply with quote

You're welcome and thanks for the feedback. icon_smile.gif
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 -> IMS DB/DC All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Problem reading GTF trace output danik56 ABENDS & Debugging 7 Thu Mar 16, 2017 1:02 pm
No new posts ROUNDED Problem with COMPUTE statement shalem COBOL Programming 11 Thu Feb 09, 2017 8:16 pm
No new posts SYMNAMES problem jacobdng DFSORT/ICETOOL 7 Thu Dec 22, 2016 7:47 am
No new posts Problem in writing Output file vickey_dw COBOL Programming 5 Mon Nov 14, 2016 11:14 pm
No new posts Problem in Running Query via JCL vickey_dw DB2 3 Tue Oct 18, 2016 11:11 pm


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