View previous topic :: View next topic |
Author |
Message |
Sreejith Intermediate
Joined: 02 Dec 2002 Posts: 155 Topics: 25 Location: N.Ireland
|
Posted: Mon Feb 28, 2005 6:55 am Post subject: making /TEST MFS the default |
|
|
Does anyone know how to make an IMS online region to look for the format in IMS.TFORMAT as default ?
I know this can be achieved by /TEST MFS command. But our testers find it "too much" entering this eveyday. I did a read of the manual and think the /ASSIGN can save user settings so that the tester can say /TEST MFS once and save this. I tried the /ASSIGN command with no luck as it always came out with missing parameter or other errors. May be I don't have access to this command.
Thanks
Sreejith |
|
Back to top |
|
 |
Bithead Advanced

Joined: 03 Jan 2003 Posts: 550 Topics: 23 Location: Michigan, USA
|
Posted: Mon Feb 28, 2005 2:31 pm Post subject: |
|
|
It may be possible to do this through your session manager. |
|
Back to top |
|
 |
Sreejith Intermediate
Joined: 02 Dec 2002 Posts: 155 Topics: 25 Location: N.Ireland
|
Posted: Tue Mar 01, 2005 3:56 am Post subject: |
|
|
thanks.. this is my session detail. couldn't find a place to say /test mfs
Code: |
Modify a Session Definition More: +
Modify session RSGIMST then press ENTER.
(APL) VTAM Appl ID......... CIM55T
(APL) Description.......... RSG IMS TEST
(USR) Display group........ 2 (9999-0000)
(APL) Display order........ 0 (9999-0000)
(USR) VTAM logmode name....
(USR) Userdata...
The following fields apply to MULTI sessions only:
(USR) Initial status....... + (D, F, or B)
(USR) Initial dialog name..
(APL) Termination dialog...
Command ===>
Enter F1=Help F4=Prompt F8=Fwd F9=Reset F12=Cancel
----------------------------------------------------------------
|
according to manual the following will do what I want. I forwarded this to the IMS sys progs and they are looking ito it.
Auto test MFS
ETO Support provides an optional Auto /TEST MFS feature. Auto /TEST MFS automatically puts every SLU2/3270, SLUP/FINANCE, or SLU1 device into /TEST MFS mode after a valid signon. The signon could be the result of:
A user entering the IMS /SIGN command
Automatic signon by ETO Support
signon data passed in the logon data by the device
The Auto /TEST MFS feature can be used in a development environment to put developers into /TEST MFS mode. This feature is controlled by device type. To enable this feature, add the following DD statement to the IMS control region JCL:
For SLU2/3270 add:
//IZTTESTM DD DUMMY
For SLU1 add:
//IZTTESTP DD DUMMY
For SLUP/FINANCE add:
//IZTTESTF DD DUMMY
The only way to activate or deactivate this option is to add/remove the DD statement(s) and restart the IMS control region. IMS test and production systems can still share the ETO Support |options data set. If you want, the Auto /TEST MFS feature can be activated in the test region by adding the DD statement; in this case, the production regions remain unaffected.
thanks
Sreejith |
|
Back to top |
|
 |
Hilltop Beginner
Joined: 14 Oct 2004 Posts: 62 Topics: 21
|
Posted: Mon Jun 27, 2005 7:29 am Post subject: |
|
|
I created a MFS and genned successfully with MFSGEN. When I try to test using /test MFS and /For modname, I am getting the following error
Quote: |
DFS057I REQUESTED BLOCK NOT AVAILABLE: 027FSCS40A RC=04
|
please advise.
Thanks. |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
|
Posted: Mon Jun 27, 2005 7:48 am Post subject: |
|
|
Hiltop,
Make sure that you are typing the right modname. Any way here is the explanation of the error code.
Code: |
DFS057I REQUESTED BLOCK NOT AVAILABLE: blockname RC = reason
Explanation: MFS cannot fetch the control blocks required to process an
output message or to process the /FORMAT request. 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.
The reason code indicates the type of failure that occurred:
Code (Hex) Meaning
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:
o There is a misspelled message output descriptor (MOD) name
or the MOD does not exist in the active format data set
library.
o 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.
|
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
Hilltop Beginner
Joined: 14 Oct 2004 Posts: 62 Topics: 21
|
Posted: Mon Jun 27, 2005 8:11 am Post subject: |
|
|
In my active format library I can see my mod and mid name. Then why /for is not fetching from it. Do I need to include my transaction in APPLCTN macro?
Please advise. |
|
Back to top |
|
 |
Bithead Advanced

Joined: 03 Jan 2003 Posts: 550 Topics: 23 Location: Michigan, USA
|
Posted: Tue Jun 28, 2005 8:46 am Post subject: |
|
|
Did you copy the staging library to the online library either at IMS re-start or with the Online Change Utility? |
|
Back to top |
|
 |
Hilltop Beginner
Joined: 14 Oct 2004 Posts: 62 Topics: 21
|
Posted: Tue Jun 28, 2005 11:51 pm Post subject: |
|
|
Nope. I did not copy anything to the staging library. At this point I have only map I did not define any transaction to it using APPLCTN. Is it necessary to add it?
This is a new screen which I am writing. My load map is in format and tformat libraries. Am I missing anything here?
Thanks.
PS: Could you please tell me what are the names of the online library. |
|
Back to top |
|
 |
Bithead Advanced

Joined: 03 Jan 2003 Posts: 550 Topics: 23 Location: Michigan, USA
|
Posted: Wed Jun 29, 2005 9:00 am Post subject: |
|
|
The active format library is either FORMATA or FORMATB. /TEST MFS uses the TFORMAT library. Check which one you are using.
The MFSUTIL procedure places the blocks in the staging library. The Online Change Utility copies these to the inactive library and the /MOD PREPARE statement is use to switch the active library. Alternatively, the recycling of IMS may rebuild the active library, depending on your shop setup.
The MFSTEST procedure places the blocks in the TFORMAT library.
The library names are shop specific so I can't help you on that.
The format of the error message seems to indicate that the MOD exists but the DIF does not. If you are looking at the correct libraries, please post you MOD statement from the MFS. |
|
Back to top |
|
 |
tigerzhaosc Beginner
Joined: 01 Aug 2006 Posts: 2 Topics: 1
|
Posted: Tue Aug 01, 2006 2:50 pm Post subject: |
|
|
I am testing my new MFS Map, got a problem. I used the /TEST MFS to test the TFORAMT Screen...however after I /END the Testing and switched back to the original version of MFS MAP ...I found the fields in the original Map is shifted...any ideas? Your help is greatly appreciated! |
|
Back to top |
|
 |
|
|