|Attachmate Synapta Services Builder for IMS Version 3.0||May 2005|
© 2005 Attachmate Corporation. All rights reserved.
This file contains late-breaking information about this release of Synapta Services Builder for IMS. Synapta Services Builder for IMS provides host access to custom applications that require transaction-based host data from IMS applications.
For more information about these features refer to the topic, What's New in Services Builder for IMS, in the Getting Started Guide.
Reboot Recommended after Uninstalling
To delete files that may be in use, Attachmate recommends rebooting your computer after uninstalling this product.
PIC 99 Clause in an ODO Structure Causing BeanGenerationException
Within a COBOL copybook, a PIC 99 clause in an ODO structure causes a BeanGenerationException. To work around this, edit your copybook to change the value of the PIC 99 clause to PIC 9(2). This causes the Bean Generator (in task Builder) to create an API for that field, which compiles and functions properly.
Working With Unnamed Items in Your COBOL Copybook
Although the COBOL compiler allows an unnamed item, to produce an accurate task file for use with Services Builder for IMS, you must edit the copybook and supply a unique data name to any unnamed items. Do this before opening the copybook in Task Builder.
For example, you would change this:
01 EMPLOYEE-RECORD. 02 OCCURS 5 TIMES. 03 EMPLOYEE-JOB-CODE PIC X(02). 03 EMPLOYEE-DEPT-CODE PIC X(03).
To this, then build your task.
01 EMPLOYEE-RECORD. 02 EMPLOYEE-TABLE OCCURS 5 TIMES. 03 EMPLOYEE-JOB-CODE PIC X(02). 03 EMPLOYEE-DEPT-CODE PIC X(03).
Naming Conventions for Task Definitions
To support Web service standards, all dash ("-") characters used in copybook field names are converted to underscore characters ("_") when they are used for constructing task definitions.
Overwriting JAR Files
When publishing JAR files to Management and Control Services (MCS), it is important that each JAR file is given a unique name. If you publish JAR files from Task Builder with the same name, the newer file will overwrite the earlier file (both on MCS and on your local machine) without warning. Published JAR files from different Attachmate components can coexist as they are stored in different locations within MCS. However, if you try to use identically named JAR files in integration projects with Attachmate products such as Presentation Builder, they will overwrite each other without warning.
Use Alphanumeric Characters Only in Task Definition Name, JAR File Name, and Package Name
When building tasks that you intend to export as a Java Bean, use only alphanumeric characters for the Task Definition Name (Task ID) and the JAR file name. Also, the first character must be a letter of the alphabet. Otherwise the bean may not compile. If it compiles, it may not run properly.
If You Cannot Generate Java Beans From Your Task Files
Although Task Builder will run if you have only the Java Runtime Environment (JRE) installed, you must have installed the Java SDK to be able to generate Java Beans.
In addition, if you have more than one version of the SDK or JRE installed, version 1.3 or later of the SDK must appear in your PATH before any earlier versions or any versions of the JRE. Otherwise, Task Builder may attempt to use the incorrect version and bean generation will fail.
In particular, you need to be aware of this issue if, after Task Builder is installed, another third-party application installs a version of the JRE and adds it to your PATH.
New Actions not Displaying on WebSphere
When adding (or copying, editing, or deleting) a runtime server, the MCS detail frame will update correctly the first time, but subsequent actions will not be displayed. Click on 'Services Builder for IMS' again to see the updated nodes and 'Runtime Servers' to see the updated list of servers.
Naming Task Definitions Used to Generate Apache Axis Web Services
WSDL files created for Apache Axis Web services aren't visible to the Task Builder if the corresponding task definition name contains lowercase letters. To avoid this situation, when creating a new task definition do not use lowercase letters in the task definition name.
Screen Resolution Settings, Hidden UI Fields
Some Task Builder text display or entry fields may be hidden from view unless your screen resolution setting is set to at least 1024 x 768 and the corresponding Task Builder window is maximized.
Spaces in java.home Results in Error
When specifying a default value for java.home, used for deploying Web services, any spaces appearing in the value specifying your installation directory will result in an error. To avoid this situation it is recommended that you modify your java.home prior to building your apache web service or to modify your deploy.cmd after building your web service. Your java.home modification should avoid the use of space characters. For example, instead of the entry "C:\Program Files", use "c:\progra~1".
Default Property Does Not Apply to Output Fields
The Default property is provided so you can create a default value corresponding to a host application input field. This property is not applicable to output fields, and will not have any effect if used.
Non-conversational Transactions Only for IMS Runtime
The current capability of the IMS Runtime is limited to non-conversational transactions—Send then Commit and Synchlevel none transaction processing.
Package Name Field Sometimes Isn't Editable
If, in the Generating page of the Options dialog box, you select Service Bean or Tasks Beans, and then go to generate them, the corresponding check boxes will be selected as expected but the Package Name field will be unavailable. To make the Package Name field available, clear and then reselect the check box for the type of bean you want to generate.
Client Access Rights Settings Not Available for Web Services
Client access rights settings (as a property of input and output fields) do not affect Web services (Apache, WebLogic, and .NET).
Use of Client Access Rights Property Settings
The Client Access Rights property for input and output fields is intended only for use with IConnectorAccess and Task Beans. In the present release there are no mechanisms to prevent operating outside of these environments.
Running Multiple Instances of the Services Builder Runtime Service
Updates to port selection capabilities have made in possible to launch multiple instances of the Services Builder run-time service. While this presents an undesirable operating situation, presently there are no limitations in place to prevent this from happening. For the current release, it is recommended that you avoid running multiple instances of the Services Builder run-time service.
Extra Click Required When Setting Field Properties
In Task Builder, when setting field properties, set the property, then click a different field before clicking the Next button; otherwise, the setting will not persist.
Precision, Scale, Translate, and Pattern Properties Do Not Persist For Some Input and Output Fields
When creating a task definition, depending on the data type for input and output fields, the settings made for precision, scale, translate, and pattern properties are not written to the task file when the task definition is saved. Consequently, these edited definitions have no effect during runtime, and are not visible if the task is re-edited.
|To display the help|