Joined: 21 Jul 2006 Posts: 50 Location: California
Hi All,
some of the our testers are getting the below messgae whenever they are putting in a specific transaction (XYZ01)
DFS057I - REQUESTED BLOCK NOT AVAILABLE RC=04
The x-action is working fine for me. It's an existing one, no new changes.
I googled DFS057I and there is quite some information but since I am new to IMS, I am not able to explain the reason behind the error.
From google -
1. The MOD name specified in a record is missing from the MFS format library.
2. The DIF/DOFs associated with the format do not match the terminal type specified in the ./D BTSIN control statement.
The issue happens in a different time Zone (almost early 3:00am for me).
I have asked them to check if the DB's are up, check the downtime of the region etc etc. but they are facing this problem from couple of days and no one seems to know the reason hence I am posting it here.
Joined: 07 Nov 2005 Posts: 1143 Location: The Netherlands at Hole 19
You have a problem with messages handled by IMS.
From the sticky where to find info about IMS you might have found this. You're testing using BTS (Batch terminal Simulator) I guess? In your BTSIN dataset correct the ./D statement if the terminal device is wrong compared to the DIF (Device Input Formats) and DOF (Device Output Formats) description in MFS. DIF/DOF tells which type of terminal are used; for DIF check here , for DOF do the search yourself But first check if the MOD (Message Output Descriptor) members are in the MFS-library.
I was having this same problem and a friend told me to look at the DEVICE, of which I was missing. I am using Telon so it might look different for you. I added DEVICE TYPE=3270-A2 This made the difference. When I recompiled I found this to be inserted after the PRINT NOGEN line. I think this is found in your MFSSRC member, but again, I'm using Telon and it has a panel for this parameter. Hope this helps!
But first check if the MOD (Message Output Descriptor) members are in the MFS-library.