Support & downloads
Search result
Feedback

Support & downloads >

IMS MFS Web Enablement Frequently Asked Questions

Forum/discussion group

Abstract

Frequently asked questions related to IMS MFS Web Enablement

Content

Q1: I have just installed and configured the instance servlet on WebSphere Application Server. I couldn’t get the initial blank page to be displayed, what’s wrong?
Here are some suggestions:

Make sure the instance servlet is installed successfully and started. Open up the WebSphere Application Server Administrative Console, expand Applications, and select Enterprise Applications. Verify the instance servlet war shows up in the list and its status shows started.
Verify the specified style sheet is in the correct location. The style sheet should be in the location specified by the MFSStyleSheet initialization parameter in the servlet application’s web.xml file. From the WebSphere Application Server Administrative Console, expand Applications and select Enterprise Applications. Select the instance servlet war. Under Related Items, select Web Modules. Select the instance servlet war. Under Additional Properties, select View Deployment Descriptor. Expand Servlet and JSPs, expand Servlet name: servlet, expand Init Parameters, and expand Param name: MFSStyleSheet for the specified file location, e.g. file:/C:\stylesheet\sample3270.xsl. If a different location is desired, re-installing the instance servlet war is required: stop, uninstall, reinstall, and start the updated instance servlet war file.
Verify the system default XMI files (DFSMI1, DFSMI2, DFSMO1, DFSMO3, DFSMO5, UNFORMATTED, and UNFORMATTEDIN) are in the correct location. The files should be in the location specified by the MFSXMLRepositoryURI initialization parameter in the servlet application’s web.xml file. Follow the previous suggest to find the specified location. Move the XMI files into the specified location. The XMI files can be found in the MFS XML Utility’s private sub-directory.
Verify that the MFS Web Enablement jar files (MFSRuntime.jar and MFSTDTDLang.jar) are in the correct location. The files should be in the location specified in the classpath of IMS Connector for Java. From the WebSphere Application Server Administrative Console, expand Resources and select Resource Adapters. Select the installed IMS resource adapter. In Classpath, verify that MFSRuntime.jar and MFSTDTDLang.jar appear before the IMS rar. Verify that the jar files are in the specified location.
Verify the URL of the instance servlet, i.e. http://nodename/context root/servlet URL.
The node name is the name of the machine on which WebSphere Application Server runs and the port number.
The context root is specified during installing the enterprise application. From the WebSphere Application Server Administrative Console, expand Applications and select Enterprise Applications. Select the instance servlet war. Under Additional Properties, select View Deployment Descriptor. Expand Web Modules and expand Web Module URI to locate the Context-root.
The servlet URL can be located in the servlet application’s web.xml file. From the WebSphere Application Server Administrative Console, expand Applications and select Enterprise Applications. Select the instance servlet war. Under Related Items, select Web Modules. Select the instance servlet war. Under Additional Properties, select View Deployment Descriptor. Expand Servlet Mappings and expand the desired servlet to locate the URL pattern.
Restart the web application; stop and start the instance servlet application.
Restart WebSphere Application Server; stop and start the server. Close all browsers. Try invoking the instance servlet on a new browser instance.

Q2: The Submit request does not respond, what should I do?

Here are some suggestions:

Verify that the host is available, IMS and IMS Connect are both up and running, and the host transaction and program are started. The host name, data store name, and port number can be located in the servlet application’s web.xml file. From the WebSphere Application Server Administrative Console, expand Applications and select Enterprise Applications. Select the instance servlet war. Under Related Items, select Web Modules. Select the instance servlet war. Under Additional Properties, select View Deployment Descriptor. Expand Servlet Mappings and expand the desired servlet to locate the dataStore, hostname, and portNumber.
Restart the web application; stop and start the instance servlet application.
Restart WebSphere Application Server: stop and start the server. Close all browsers. Try invoking the instance servlet on a new browser instance.
Consider setting execution timeout and/or socket timeout to properly timeout in the case that IMS Connect or host program does not respond. Regenerate the instance servlet war by running the MFS XML Utility to set the optional timeout parameters to a fixed interval, e.g. 5000 msec. Reinstall the enterprise application.

Q3: The Submit request returns a RACF error. How do I retry with a different RACF userid, password, or group name?

On the current screen, click on Reset to go to the blank page.
Enter desired RACF user id, password, and group name into the text fields.
Enter supported command or transaction request and submit.
Note: The Submit request will close existing (conversational) connection and recreate a new connection with the supplied RACF credentials.

Q4: Why am I unable to refresh or open a new window using File->New->Window (Ctrl+N)?

MFS Web Enablement keeps track of state by associating each response page with a unique index that is sent in with the next request. Refresh should not be used and error will be returned. All requests should be invoked with the supported buttons. Each browser instance can not share the same session ID, which happens when browsers are opened with File->New->Window or Ctrl+N. For Internet Explorer, users can open new browser by double clicking on the .EXE.

Q5: What is the function of each button?

Submit: submit the input data
Clear Fields: clear the contents of all input fields
Next Page: display the next physical page (equivalent to the PA1 button in 3270 terminal)
Reset: display the blank page where a command or a transaction can be entered (equivalent to the CLEAR button in 3270 terminal).
Logout: close the connection and exit
Help: display MFS Web Enablement User's Guide and Reference web page. You can change the URL in the style sheet's embedded JavaScript function: "goToURL" to direct user to another desired web page.

For example, the URL is changed to your company's Web page as the following:

function goToURL()
{
myWindow = open("","newwin","height=600,width=920,resizable=1");
myWindow.location = “http://www.yourcompany.com/homepage/";
}

Q6: Can I customize the name of the buttons displayed?

Yes, you can make proper changes to the style sheet:

For regular HTML button (as generated by sample3270.xsl), you can change the 'value' attribute to the desired name.

For example, value "Reset" of the “resetButton” is changed to Clear as the following:

<input type="submit" name="resetButton" value="Clear" class="buttonStyle2"/>

For the HTML button overlaid with image (as generated by sampleWeb.xsl), you can replace with the desire image file name in the 'src' attribute. Make sure you properly package the image file into the WAR file.

For example: image file “clear.gif” is used instead of “reset.gif” for "resetButton", the style sheet should be changed as the following:


<input type="image" name="resetButton" src="PICS/clear.gif" alt="back to the blank page where a command or a transaction can be entered" title="back to the first session where a command or a transaction can be entered" onclick="submitImageButton('resetButton')"/>
<input name="resetButton" type="hidden"/>

The war file should have the new image file “clear.gif” in the PICS folder as the following:

Note: The name of the HTML buttons should NOT be changed.

Q7. Can I customize the infopops for each button?

Yes, you can customize the style sheet:

For each HTML button (as generated by sample 3270.xsl), you can edit the 'alt' and 'title' attributes with your desired text.

For example, you could change the Next button's infopop to be "Next physical page" by editing the text to read:

<input type="submit" name="PA1Button" value="Next Page" alt=

"

Next physical page

"

title=

"

Next physical page

"

class="buttonStyle2" />

Q8. What is the recommended screen resolution to use with the sample style sheet?

The sample style sheet is good for screen resolution 1024 x 768 and 1280 x 1024.

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Document information


Product categories:

	Software

	Data Management

	Data Servers (Database Management Systems)

	IMS


Operating system(s):
	z/OS

Software version:
	9.1

Reference #:
	7008376

IBM Group:
	Software Group

Modified date:
	2009-01-08

Translate My Page

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.