View previous topic :: View next topic
|
Author |
Message |
chowdhrykapildev
New User
Joined: 05 Aug 2009 Posts: 44 Location: Hyderabad
|
|
|
|
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 |
|
|
chowdhrykapildev
New User
Joined: 05 Aug 2009 Posts: 44 Location: Hyderabad
|
|
|
|
I can also see that the related MYSSAAE, MYSSAAF Tformat modules are present in the IMS standard dataset library. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
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 |
|
|
Sandy Zimmer
Active Member
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
|
|
|
|
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 |
|
|
Sandy Zimmer
Active Member
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
|
|
|
|
One more thought - when you compiled your MFS, did it indicate a clean compile with the "CREATED" message? |
|
Back to top |
|
|
chowdhrykapildev
New User
Joined: 05 Aug 2009 Posts: 44 Location: Hyderabad
|
|
|
|
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 |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
You're welcome and thanks for the feedback. |
|
Back to top |
|
|
|