This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to

as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This

Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or

duplicated, in whole or in part, without the prior written consent of CA.

If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents About the Web Services Consumption Feature ............................................................................................ 6

Web Services Consumption Feature Documentation ................................................................................... 6

Add a CALL EXTERNAL Statement ............................................................................................................. 6

XML Types ............................................................................................................................................. 8

Recommended Gen Data Type Choices for XSD Data Types .............................................................. 11

CALL EXTERNAL Format....................................................................................................................... 13

Change the Method Parameter Matching .......................................................................................... 13

To Copy Action Statements ................................................................................................................. 14

To Xcopy Action Statements from/to Multiple Action Diagrams ....................................................... 14

To Xcopy Action Statements from/to Single Action Diagrams ........................................................... 15

Context-Sensitive Help Topics................................................................................................................. 17

Select WSDL Method .......................................................................................................................... 17

Web Service Parameter Matching ...................................................................................................... 19

Create/ Select View ............................................................................................................................. 21

Method Parameter ............................................................................................................................. 22

Cannot Perform an External Call ......................................................................................................... 23

Duplicate Match .................................................................................................................................. 23

Invalid View Name .............................................................................................................................. 24

Error Message ..................................................................................................................................... 24

SOAPAction Missing ............................................................................................................................ 24

Service Missing .................................................................................................................................... 25

Messages ................................................................................................................................................. 25

TIRM301E - Error insufficient memory to perform external call ........................................................ 25

TIRM302E - Error deallocation error performing external call ........................................................... 25

TIRM303E - Error invalid handle trying to perform external call ........................................................ 25

TIRM304E - Error invalid (NULL) value trying to perform external call .............................................. 25

TIRM305E - Error could not locate value trying to perform external call ........................................... 25

TIRM306E - Error invalid conversion trying to perform external call ................................................. 26

TIRM307E - Error value exceeds maximum digits performing external call ....................................... 26

TIRM308E - Error value exceeds maximum length performing external call ..................................... 26

TIRM309E - Error invalid value performing external call .................................................................... 26

TIRM310E - Error invalid name trying to perform external call .......................................................... 26

TIRM311E - Error invalid namespace trying to perform external call ................................................ 26

TIRM312E - Error invalid occurrence given trying to perform external call ....................................... 27

TIRM313E - Error invalid SOAPType performing external call ............................................................ 27

TIRM314E - Error invalid operation name performing external call ................................................... 27

TIRM315E - Error invalid URL performing external call ...................................................................... 27

TIRM316E - Error invalid SOAPAction performing external call ......................................................... 27

TIRM317E - Error invalid parent ID performing external call ............................................................. 27

TIRM318E - Error duplicate UID performing external call .................................................................. 28

TIRM319E - Error invalid XMLType performing external call .............................................................. 28

TIRM320E - Error invalid occurs value performing external call ........................................................ 28

TIRM321E - Error invalid parent element type performing external call ........................................... 28

TIRM322E - Error occurred while performing external call ................................................................ 28

TIRM323E - Error UID could not be located performing external call ................................................ 28

TIRM324E - Error invalid RGV level performing external call ............................................................. 29

About the Action Diagram BLOB Functions Feature ................................................................................... 29

Action Diagram BLOB Functions Feature Documentation .......................................................................... 30

Functions - BLOB Functions in Action Diagram ....................................................................................... 30

Concatblob .......................................................................................................................................... 30

Substrblob ........................................................................................................................................... 31

blobdbcs .............................................................................................................................................. 31

blobmbcs ............................................................................................................................................. 32

blobtext ............................................................................................................................................... 32

dbcsblob .............................................................................................................................................. 32

mbcsblob ............................................................................................................................................. 33

textblob ............................................................................................................................................... 33

Functions - Numeric Functions in Action Diagram.................................................................................. 33

Lengthblob .......................................................................................................................................... 33

BLOB Functions in Action Diagram ......................................................................................................... 35

About the Toolset Completions String Manager Feature ........................................................................... 36

Toolset Completions String Manager Feature Documentation .................................................................. 36

Context –Sensitive Help Topic in Toolset ................................................................................................ 36

Confirmation Message ........................................................................................................................ 36

Messages in Gen Studio .......................................................................................................................... 37

Unable to Open the Model in CA Gen Studio ..................................................................................... 37

About the Web Services Consumption Feature CA Gen provides the facility to consume SOAP Web Services using the Call External statement in an

action diagram.

To use the new Web Service Consumption functionality with existing 9.2.A6 models, the encyclopedia

schema tables must be updated and the models run through model conversion as follows:

■ For the Client-Server Encyclopedia, reload the schema tables by running the CSE Configuration with the Update Encyclopedia option.

■ For the Host Encyclopedia, reload the schema tables by running CEJOB05 (or CAJOB05) again after applying and deploying WKS85001.

■ Convert models into 9.2.A6 schema.

The new Web Service Consumption functionality supports C and Java languages only.

Note: The CALL EXTERNAL statement cannot be copied into another action diagram, and an

action diagram containing a CALL EXTERNAL statement must not be copied until a known issue

is addressed.

Web Services Consumption Feature Documentation in Toolset Help

Add a CALL EXTERNAL Statement

CALL EXTERNAL statements enable Toolset to consume web services.

Follow these steps:

1. Click Analysis or Design, Action Diagram.

The Action Diagram Names dialog opens.

2. Select an item from the list of Processes, Procedure Steps, or Action Blocks, and click OK.

The Action Diagram window opens.

3. Select the blank line that is immediately after the views section and click Edit, Add

Statement, Call External.

The Select WSDL Method dialog opens.

4. Click the push button next to the WSDL URI field to browse the file.

The Windows File Open dialog opens with File name field initialized with ‘*.wsdl’

extension. Also, the files listed in the Windows File Open dialog are initially filtered with

the extension ‘wsdl’, and you can change it from the drop-down list next to the file

name entry field.

5. Select the appropriate file and click Open.

6. Click Go.

Note: You can also enter the file path or URI in the WSDL URI field and click Go.

For example, the following WSDL path can be entered in the WSDL URI field:

http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?wsdl

Only the methods that support SOAP 1.1 or 1.2 bindings for the Web service are

retrieved and listed. If both the bindings are available, methods that have SOAP 1.2

binding will take priority over SOAP 1.1 binding.

If the specified WSDL file is not accessible or it is not valid, an error message is

displayed.

7. Select the method and click Add.

The Import Web Service Parameter Matching dialog opens.

8. Follow one of these steps to match the parameters:

To automatically match the parameters, click Default.

The parameters from the WSDL Parameters list are matched to a new work view.

Note: Using this option will override the existing matches.

Note: For more information about the various Gen data types and XSD data

types, see XML Data Types. For more information about which XSD data type is

matched with which Gen data type when the Default button is clicked, see

Recommended Gen Data Type Choices for XSD Data Types.

Select a parameter from the WSDL Parameters list and select an existing

attribute view to match to it, or select a data model attribute or work set attribute to

have the toolset create an attribute view for you. Click Match.

The selected parameter and the matched attribute are added in the Parameter and

Views columns respectively.

Note: To unmatch a parameter and an attribute, select the row in the Parameter and

Views table and click Unmatch.

9. Click OK.

The Export Web Service Parameter Matching dialog opens.

10. Repeat steps 8 and 9 for output parameters, if needed.

The output parameters for a WSDL method may only match to the export views of an

action diagram, or to the import views that are marked as “Used as both input and

output”.

Note: You can match a Gen BLOB view to a method string parameter on import or

export so that data larger than 4094 characters are sent to or returned from the method

call.

11. Click OK.

The CALL EXTERNAL statement is added with the specified parameters.

The statement is displayed as CALL EXTERNAL followed by the type of external call being

made (for example “Web Service”), followed by the method name.

Note:

If the action diagram has any statements other than NOTE statements in it, the

menu option for adding a Call External statement is disabled.

You cannot add a CALL EXTERNAL statement in an action diagram that has local

or entity action views. To add a CALL EXTERNAL statement, the action diagram must

only have import and export views.

After adding a CALL EXTERNAL statement, the only statements that are allowed

to be added in that action diagram are NOTEs and blank lines.

CALL EXTERNAL statement is valid only for C application; it does not support

COBOL, C#, and JAVA applications.

CALL EXTERNAL statement does not support NonStop operating system.

XML Types

The following table shows XML Type followed by GenType for the inbound matching:

XML Type Gen Type

string text, numeric, date, time, timestamp, BLOB

boolean text, numeric

decimal text, numeric

float text, numeric

double text, numeric

duration text

dateTime text, numeric, date, time, timestamp

time text, numeric, time

date text, numeric, date

gYearMonth text, date, timestamp

gYear text, date, timestamp

gMonthDay text, date, timestamp

gDay text, date, timestamp

gMonth text, date, timestamp

hexBinary text, BLOB

base64Binary text, BLOB

anyURI text

QName text

NOTATION text

integer text, numeric, date, time

nonPositiveInteger text, numeric

negativeInteger text, numeric

long text, numeric, date, time

int text, numeric, date, time

short text, numeric

byte text, numeric

nonNegativeInteger text, numeric, date, time

unsignedLong text, numeric, date, time

unsignedInt text, numeric, date, time

unsignedShort text, numeric

unsignedByte text, numeric

positiveInteger text, numeric, date, time

The following table shows Gen Type followed by XML Type for outbound matching:

GenType XML Type

text string, duration, time, dateTime, date, gYearMonth,

gYear, gMonthDay, gDay, gMonth, boolean,

base64Binary, hexBinary, float, decimal, double, anyURI,

QName, NOTATION, integer, nonPositiveInteger,

negativeInteger, long, int, short, byte,

nonNegativeInteger, unsignedLong unsignedInt,

unsignedShort unsignedByte, positiveInteger

numeric string, date, time, boolean, float, decimal, double,

integer, nonPositiveInteger, negativeInteger, long, int,

short, byte, nonNegativeInteger, unsignedLong,

unsignedInt, unsignedShort unsignedByte,

positiveInteger

date string, dateTime, date, gYearMonth, gYear, gMonthDay,

gDay, gMonth, integer, long, int, nonNegativeInteger,

unsignedLong, unsignedInt, positiveInteger

time string, time, dateTime, integer, long, int,

NonNegativeInteger, unsignedLong, unsignedInt,

positiveinteger

timeStamp string, dateTime, gYearMonth, gYear, gMonthDay, gDay,

gMonth

BLOB base64Binary, hexBinary, String

Note: For more information, see http://www.w3.org/TR/xmlschema-2/#built-in-primitive-

datatypes and http://www.w3.org/TR/xmlschema-2/#built-in-derived

Recommended Gen Data Type Choices for XSD Data Types

The following table contains the recommended Gen data type match for every XSD data type.

These matches are also used while creating work set views when you click the Default button

on the Import or Export Web Service Parameter Matching dialog.

XSD Data Type Gen Data Type

string Text (length = 4094, varying = true, case-sensitive = true)

anyURI Text (length = 1000, varying = true, case-sensitive = true)

QName Text (length = 1000, varying = true, case-sensitive = true)

NOTATION Text (length = 1000, varying = true, case-sensitive = true)

duration Text (length = 100, varying = false, case-sensitive = false)

boolean Number (1)

base64Binary BLOB (length = 2GB)

hexBinary BLOB (length = 2GB)

float Number (length = 15, decimal points = 6, decimal precision =

false)

double Number (length = 15, decimal points = 6, decimal precision =

false)

decimal Number (length = 18, decimal points = 6, decimal precision =

true)

integer Number (length = 18, decimal points = 0, decimal precision =

true)

long Number (length = 18, decimal points = 0, decimal precision =

true)

int Number (length = 10, decimal precision = false)

short Number (length = 5)

byte Number (length = 3)

nonPositiveInteger Number (length = 18, decimal points = 0, decimal precision =

true)

nonNegativeInteger Number (length = 18, decimal points = 0, decimal precision =

true)

negativeInteger Number (length = 18, decimal points = 0, decimal precision =

true)

positiveInteger Number (length = 18, decimal points = 0, decimal precision =

true)

unsignedLong Number (length = 18, decimal points = 0, decimal precision =

true)

unsignedInt Number (length = 10, decimal points = 0, decimal precision =

false)

unsignedShort Number (length = 5)

unsignedByte Number (length = 3)

dateTime Timestamp

time Time

date Date

gYearMonth Date

gYear Date

gMonthDay Date

gDay Date

gMonth Date

CALL EXTERNAL Format

The action diagram CALL EXTERNAL statement is used to call a web service interface in the

following format:

CALL EXTERNAL <type of external call> <method name>

<type of external call>

Specifies the type of external call being made by the statement. One of the types of external

call being made is Web Service.

<method name>

Specifies the WSDL method name.

For example: The type of external call being made in the following example is Web Service and the method name is GetQuote:

-EXAMPLE_ACTION_BLOCK

| IMPORTS:

| EXPORTS:

| LOCALS:

| ENTITY ACTIONS:

| CALL EXTERNAL Web Service “GetQuote”

Change the Method Parameter Matching

The input and output parameters of a method are matched with the attribute views, data

model attribute, or work set attribute. After matching the views and the parameters, you may

want to change the matching at a later time.

Follow these steps:

1. Click Analysis or Design, Action Diagram.

The Action Diagram Names dialog opens.

2. Select an action diagram containing a CALL EXTERNAL statement and click OK.

The action diagram opens.

3. Select the method whose parameter matching you want to change.

4. Click Detail, Properties.

The Method Parameter dialog opens. The input parameters and its view matching are displayed

in the Matched Input area. The operations of adding matches and deleting matches are

available below the table. Similarly, the Matched Output area contains the output parameters

and their matches, and the operations that can be performed on them.

5. Make the necessary changes and click OK.

The changes are saved.

To Copy Action Statements

You may want to copy action statements within an action diagram to replicate their

functionality.

Follow these steps:

1. Click Analysis or Design, Action Diagram.

The Action Diagram dialog is displayed.

2. Select an item from the list of Processes, Procedure Steps, or Action Blocks, and click OK.

The Action Diagram window opens.

To copy one statement, select entire statement. Click Edit, Copy.

To copy a block of statements, select first statement to copy, <Shift>, last statement in

block, click Edit, Copy.

To copy multiple non-contiguous statements, select first statement to copy, <Ctrl>, each

additional statement to be copied, click Edit, Copy.

Note: If you select a CALL EXTERNAL statement, the menu item Edit, Copy is disabled because

Copy is not allowed for CALL EXTERNAL statements.

To Xcopy Action Statements from/to Multiple Action Diagrams

You may want to copy action statements of many action diagrams into one or more action

diagrams to replicate their functionality.

Follow these steps:

1. Click Analysis or Design, Action Diagram.

The Action Diagram dialog is displayed.

2. Select first source action diagram (process, procedure step) or action block, select second source

process, procedure step, or action block. Continue to select as many source action diagrams and action

blocks as needed.

3. Click OK after each selection.

To copy a single one-line statement, select it by clicking the left mouse button one time.

To copy a multi-line statement, select the first line of statement to copy, <Shift>, last

line statement in block. (Drag select also selects all lines of statement.)

To copy multiple non-contiguous statements, select first statement to copy, <Ctrl>,

select each additional statement that you want to copy.

4. Click Diagram, Launch, Action Diagram.

The Action Diagram Names dialog is displayed.

5. Select a name of destination action diagram or action block, and click OK. Continue to select as

many destination action diagrams and action blocks as needed, and click OK after each selection.

6. Select a line in destination after which you want to copy the selected action statement from

each source action diagram or action block.

7. Click Edit, Xcopy.

8. Select a source action diagram to copy from, click Xcopy. Select the second source action

diagram to copy from, and click Xcopy. Continue to select as many source action diagrams as needed

and click Xcopy.

Note: If you select a CALL EXTERNAL statement, the menu item Edit, Xcopy is disabled because

Xcopy is not allowed for CALL EXTERNAL statements.

To Xcopy Action Statements from/to Single Action Diagrams

You may want to copy action statements of an action diagram into another action diagram to

replicate their functionality.

Follow these steps:

1. Click Analysis or Design, Action Diagram.

The Action Diagram dialog is displayed.

2. Select the name of a single source action diagram (process, procedure step) or action block, and

click OK.

To copy a single one-line statement, select it by clicking the left mouse button one time.

To copy a multi-line statement, select the first line of statement to copy, <Shift>, last

line statement in block. (Drag select also selects all lines of statement.)

To copy multiple non-contiguous statements, select first statement to copy, <Ctrl>, each

additional statement to be copied.

3. Click Diagram, Launch, Action Diagram.

The Action Diagram Names dialog is displayed.

4. Select a name of destination action diagram or action block. Click OK, line in destination after

which to copy the selected action statement from the source, click Edit, Xcopy.

Note: If you select a CALL EXTERNAL statement, the menu item Edit, Xcopy is disabled because

Xcopy is not allowed for CALL EXTERNAL statements.

Context-Sensitive Help Topics

Select WSDL Method

This dialog lets you import a web service method.

This dialog contains the following items:

WSDL URI

Specify the file path or URI of a WSDL in the following ways:

You can type the URI of the WSDL.

Click the ... button beside this field to navigate to the location of the WSDL file in your

local computer or on a network. Initially the File Open dialog box only displays the .wsdl, .xml,

and .txt file formats. You can change the file type by selecting from the dropdown to include all

file types. The path is reformatted with the “file:///” URI form.

Start typing the path and existing WSDL paths that match the text are displayed in the

dropdown list. Select a path from the dropdown.

Click Go to display the list of methods that support SOAP 1.1 or 1.2 bindings for the WSDL.

Select a method from the list.

Add

Adds the method to the model (if it did not already exist). This button is enabled when a

method is selected.

Cancel

Exits the dialog without performing any action.

Web Service Parameter Matching

This dialog lets you match the views, data model attributes, or work set attributes to the WSDL

input and output parameters.

This dialog contains the following items:

Parameter and Views

Displays the list of parameters and their matched views.

WSDL Parameters

Select the WSDL input or output parameters to match with an action diagram view.

Views, Attributes and Work Sets

Select an attribute view, data model attribute, or work set attribute that you want to match

with the selected parameter.

Default

Creates a work set attribute with the name of the method and an import view of that work set,

in case of import web service parameter matching. Creates a work set attribute with the name

of the method and an export view of that work set, in case of export web service parameter

matching. The work set is then automatically matched with the method parameters. In case of

repeating group views, a repeating group view of size 10 is created and a separate repeating

group is created for each individual parameter, if the grouping is not obvious. This option

simplifies the need for explicit parameter matching.

Note: Using this option will override the existing matches.

Note: For more information about the various Gen data types and XSD data types, see XML

Data Types. For more information about which XSD data type is matched with which Gen data

type when the Default button is clicked, see Recommended Gen Data Type Choices for XSD

Data Types.

Match

Matches the selected parameter with a selected attribute view, data model attribute, or work

set attribute. The selected items are added to the Parameter and Views table. The parameter is

removed from the WSDL Parameters list. This button is enabled only if a compatible

combination is selected. If a data model attribute or work set attribute is selected, a dialog

opens. In the dialog, you can either name the view and add the attribute in the view, or select

from a list of existing views of the entity type or work set to add the attribute into. The match is

then displayed in the Parameter and Views table. The changes are updated in the model.

If the WSDL parameter is optional, we recommend that you mark the matched predicate view

as nullable using View Maintenance, that is, minOccurs=0 or nillable (nillable=true). The

NullIndicator of the matched predicate view can be used to verify if the matching parameter

value is missing or nil in the executing Web Service method response.

Unmatch

Removes the selected items from the Parameter and Views table, that is, the matches are

cleared. The parameter is added back to the list of parameters that need to be matched. This

button is enabled when one or more entries in the Parameter and Views table are selected.

OK

Closes the dialog and updates the model.

Create/ Select View

This dialog lets you name the view in which you can add the attribute or select from a list of

existing views of the entity type or work set to add the attribute into.

This dialog contains the following fields:

View Name

Specify the view name. Type a name for a new view or select a name of an existing view from

the dropdown menu.

OK

Adds the view, closes the dialog, and displays the view and its matching parameter in the Web

Service Parameter Matching dialog.

Cancel

Exit the dialog without performing any change.

Method Parameter

This dialog lets you change the parameter matching. The input parameters and its view

matching are displayed in the Matched Input area. The operations of adding matches and

deleting matches are available below the table. Similarly, the Matched Output area contains

the output parameters and their matches, and the operations that can be performed on them.

This dialog contains the following fields:

View and Parameter

Displays a list of views and its matched parameters.

Add

Creates a mapping between the method parameters and the views in the action diagram.

Opens the Web Service Method Parameter dialog.

Delete

Deletes the selected view and parameter matching. This button is enabled when one or more

items in the View and Parameter table are selected.

OK

Closes the dialog after saving the changes.

Cancel

Exits the dialog without performing any changes.

If you used the Default button option to match the parameters in the Web Service Parameter

Matching dialog, a set of work sets is created. Later, you delete the matching by double-clicking

the Call External statement and click Delete in the Method Parameter dialog. When you click

the Cancel button in the Method Parameter dialog, the matching is deleted but the work sets

that were created for the parameter matching are not deleted.

Cannot Perform an External Call

This message appears when the model or a subset of the model that is being edited in the

Toolset has not been run through the optional 8.5 conversion process. This conversion process

adds objects that support the ability to use the Call External statement to converted models.

Note: For more information about model conversion, see the Client Server Encyclopedia User

Guide.

Duplicate Match

This error message indicates that the selected predicate view is already matched with one of

the WSDL parameters. Either use a different view name or select another predicate view.

Invalid View Name

This error message indicates that the view name is invalid. A view name cannot have special

characters. But the view name can contain dot (.) only to include an attribute name. The view

name in itself containing a dot (.) is not valid.

Error Message

A view exists with the name you entered. Duplicate view names are not allowed in the subset.

Type a unique name or delete the existing view name.

SOAPAction Missing

This error message indicates that the SOAPAction HTTP request header field for one or more

methods in the WSDL is missing. The SOAPAction field indicates the intent of the SOAP HTTP

request. The value of the field is a URI. The HTTP client uses this field to issue SOAP HTTP

Requests. For more information about the SOAPAction field, see http://www.w3.org/TR/wsdl.

Ensure all the methods contain the SOAPAction field.

Service Missing

This error message indicates that the WSDL service element is missing. The WSDL service

element defines a collection of ports that expose a particular binding. For more information

about the WSDL service element, see http://www.w3.org/TR/wsdl.

Ensure that the WSDL service element is available.

Messages

TIRM301E - Error insufficient memory to perform external call

Type: Fatal Error

This message indicates that enough memory is not available for performing an external call.

Clear memory and perform the external call again.

TIRM302E - Error deallocation error performing external call

Type: Fatal Error

This message indicates that a deallocation error occurred while performing an external call.

TIRM303E - Error invalid handle trying to perform external call

Type: Fatal Error

This message indicates that an invalid handle was trying to perform an external call.

Specify the correct handle and perform the external call again.

TIRM304E - Error invalid (NULL) value trying to perform external call

Type: Fatal Error

This message indicates that a NULL value was trying to perform an external call.

Correct the value and perform the external call again.

TIRM305E - Error could not locate value trying to perform external call

Type: Fatal Error

This message indicates that CA Gen could not locate the value that was trying to perform an

external call.

TIRM306E - Error invalid conversion trying to perform external call

Type: Fatal Error

This message indicates that an invalid conversion occurred while trying to perform an external

call.

TIRM307E - Error value exceeds maximum digits performing external call

Type: Fatal Error

This message indicates that the value trying to perform an external call exceeds the maximum

number of digits that was specified.

Change the length of the Attribute in the Properties dialog.

TIRM308E - Error value exceeds maximum length performing external call

Type: Fatal Error

This message indicates that the value trying to perform an external call exceeds the maximum

number of characters that was specified.

Change the length of the Attribute in the Properties dialog.

TIRM309E - Error invalid value performing external call

Type: Fatal Error

This message indicates that an invalid value was trying to perform an external call.

Correct the value and perform the external call again.

TIRM310E - Error invalid name trying to perform external call

Type: Fatal Error

This message indicates that a value with an invalid name was trying to perform an external call.

Correct the name and perform the external call again.

TIRM311E - Error invalid namespace trying to perform external call

Type: Fatal Error

This message indicates that an invalid namespace was specified while trying to perform an

external call.

Correct the namespace and perform the external call again.

TIRM312E - Error invalid occurrence given trying to perform external call

Type: Fatal Error

This message indicates that an invalid occurrence was specified while trying to perform an

external call.

TIRM313E - Error invalid SOAPType performing external call

Type: Fatal Error

This message indicates that an invalid SOAPType was specified while performing an external

call.

Correct the SOAPType and perform the external call again.

TIRM314E - Error invalid operation name performing external call

Type: Fatal Error

This message indicates that an invalid operation name was specified while performing an

external call.

TIRM315E - Error invalid URL performing external call

Type: Fatal Error

This message indicates that an invalid URL was specified while performing an external call.

Correct the URL and perform the external call again.

TIRM316E - Error invalid SOAPAction performing external call

Type: Fatal Error

This message indicates that an invalid SOAPAction was specified while performing an external

call.

Correct the SOAPAction and perform the external call again.

TIRM317E - Error invalid parent ID performing external call

Type: Fatal Error

This message indicates that an invalid parent ID was specified while performing an external call.

Correct the parent ID and perform the external call again.

TIRM318E - Error duplicate UID performing external call

Type: Fatal Error

This message indicates that a duplicate UID was specified while performing an external call.

TIRM319E - Error invalid XMLType performing external call

Type: Fatal Error

This message indicates that the XMLType that was specified while performing an external call

was invalid.

Correct the XMLType and perform the external call again.

TIRM320E - Error invalid occurs value performing external call

Type: Fatal Error

This message indicates that the occurs value that was specified while performing an external

call was invalid.

TIRM321E - Error invalid parent element type performing external call

Type: Fatal Error

This message indicates that the parent element type that was specified while performing an

external call was invalid.

Correct the parent element type and perform the external call again.

TIRM322E - Error occurred while performing external call

Type: Fatal Error

This message indicates that an error occurred while performing an external call.

TIRM323E - Error UID could not be located performing external call

Type: Fatal Error

This message indicates that the UID specified while performing an external call could not be

found.

TIRM324E - Error invalid RGV level performing external call

Type: Fatal Error

This message indicates that the RGV level specified while performing an external call was

invalid.

About the Action Diagram BLOB Functions Feature With CA Gen Release 8.5, the second phase of BLOB support provides the ability to store BLOBs in a

database, fetch BLOBs from a database, and to include BLOBs in views so that they can be passed

around in the generated application (including external action blocks). This functionality does not

include presenting or collecting BLOB data at the user interface, the file system interface, or any other

system interface.

The BLOB functions let you concatenate BLOBs together, split them apart, get their length, and convert

them to and from text data types. The following BLOB functions are available:

concatblob - concatenate two BLOBs together

substrblob - split part of a BLOB from a larger one

lengthblob - return the length of the given BLOB

blobdbcs - convert a DBCS type into a BLOB type

blobmbcs - convert an MBCS type into a BLOB type

blobtext - convert a TEXT type into a BLOB type

dbcsblob - convert a BLOB type into a DBCS type

mbcsblob - convert a BLOB type into an MBCS type

textblob - convert a BLOB type into an MBCS type

Notes:

■ These functions are implemented as user-added functions and thus are only added to the model when the function is actually used. For more information about how the functions are implemented, see the User-Added Functions in Action Diagram article.

■ For more information about the BLOB Functions in an action diagram, see the Toolset Help.

Because most of the CA Gen target databases support the BLOB data type, you can now leverage that

support within your applications.

Some points to consider when using BLOBs in CA Gen Release 8.5 include:

■ One or more BLOB attributes can be included in views that are defined as IMPORT, EXPORT, ENTITY ACTION, or LOCAL.

■ The BLOB attributes are always variable length.

■ The BLOB attributes are specified as optional or mandatory the same way as other attribute types.

■ The BLOB views are passed to and from procedure steps and action blocks (including external action blocks).

■ Operations on BLOBs in the action diagrams are limited to setting their value to NULL or to the value of another BLOB and comparing them to NULL.

■ BLOBs are supported on the following technologies:

Windows / C / Oracle, DB2, SQL Server (ODBC)

UNIX or LINUX / C / Oracle, DB2

CLR / C# / ADO.NET - Oracle, DB2, SQL Server

JVM / JAVA / JDBC - Oracle, DB2, SQL Server

■ BLOB attribute views can be used in all SQL statements (CREATE, READ, UPDATE, DELETE) and in non-SQL statements (SET, USE…) that operate on entity views.

Notes:

■ BLOB attribute views are not placed on a screen or a window/dialog.

■ BLOB attribute views are not used as identifiers nor they be used as classifying attributes in a partitioning.

■ Non-BLOB attribute views cannot be set to BLOB attribute view values and BLOB attribute views cannot be set to non-BLOB attribute view values.

Action Diagram BLOB Functions Feature Documentation in Toolset Help

Functions - BLOB Functions in Action Diagram

The following is a list of BLOB functions that let you add algorithms to the logic in action

diagrams and action blocks. Use these functions to manipulate BLOBs:

concatblob

substrblob

blobdbcs

blobmbcs

blobtext

dbcsblob

mbcsblob

textblob

Concatblob

This function concatenates two BLOB attributes. Inputs are two BLOB views. The inputs and the

output can be as large as the largest blob field that is supported by CA Gen. If the length of the

concatenated views would be greater than the length of the target view, the resulting BLOB is

truncated to the length of the target view.

INPUT: blob1 DOMAIN: BLOB

INPUT: blob2 DOMAIN: BLOB

OUTPUT: output_blob DOMAIN: BLOB

FORMAT: concatblob(blob1,blob2)

Example:

The following code sets a BLOB attribute to the BLOB which is the result of the concatenation of

three input BLOBs:

SET export work blob TO concatblob(concatblob(input1 work blob,

input2 work blob),input3 work blob

Substrblob

This function extracts the contents of a BLOB starting at a specified position and having a

certain length. If the length of the blob returned by the substrblob function is greater than the

length of the target blob, the resultant will be truncated to the length of the target blob. If the

length given as a parameter to the substrblob function is greater than the length of the amount

of data left from the starting position, then the length is the difference between the starting

position and the length of the input blob function. Inputs consist of the following parameters:

The BLOB view to be manipulated

The number or numeric view that is the starting index for the substring

The number or numeric view that is the length of the substring BLOB

The output is a BLOB value.

INPUT: input_blob DOMAIN: BLOB

INPUT: starting_index DOMAIN: number

INPUT: substring_length DOMAIN: number

OUTPUT: output_blob DOMAIN: BLOB

FORMAT: substrblob (input_blob,starting_index, substring_length)

Example:

The following code sets a BLOB attribute to the BLOB which is the result of the substring of the

import blob at the given starting position for the given length:

SET export work blob TO substrblob (import work_blob, start_index,

length_of _substr)

blobdbcs

This function converts a BLOB view to a double-byte character string. Input is a BLOB view.

Output is a double-byte character string.

INPUT: input_blob: blob

OUTPUT: output_string: text

FORMAT: blobdbcs (blob)

Example:

The following code sets a double-byte character string to the BLOB which converts a BLOB view

to a double-byte character string:

SET <export dbcs text view> TO blobdbcs (<import blob view>)

blobmbcs

This function converts a BLOB view to a mixed character string. Input is a BLOB view. Output is a

mixed text character string.

INPUT: input_blob: blob

OUTPUT: output_string: text or mixed text

FORMAT: blobmbcs (blob)

Example:

The following code sets a mixed character string to the BLOB which converts a BLOB view to a

mixed character string:

SET <export mixed text view> TO blobmbcs (<import blob view>)

blobtext

This function converts a BLOB view in a BLOB-domain attribute to a character string in a text-

domain attribute. Input is a BLOB view. Output is a character string.

INPUT: input_blob DOMAIN: BLOB

OUTPUT: string DOMAIN: text

FORMAT: blobtext (blob)

Example:

The following code sets a character string to the BLOB which converts a BLOB view to a

character string:

SET <export char view> TO blobtext (<import blob view>)

dbcsblob

This function converts a double-byte character string to a BLOB view. Input is a double-byte

character string. Output is a BLOB view.

INPUT: input_string: text

OUTPUT: output_blob: blob

FORMAT: dbcsblob (blob)

Example:

The following code converts a double-byte character string to a BLOB. This conversion is a byte-

by-byte copy of the double-byte character string to a BLOB:

SET <export BLOB view> TO dbcsblob (<import DBCS text view>)

mbcsblob

This function converts a mixed character string to a BLOB. Input is a mixed text character string.

Output is a BLOB view.

INPUT: input_string: text or mixed text

OUTPUT: output_blob: blob

FORMAT: blobmbcs (blob)

Example:

The following code converts a mixed character string to a BLOB. This conversion is a byte-by-

byte copy of the mixed character string to a BLOB:

SET <export blob view> TO mbcsblob (<import mbcs text view>)

textblob

This function converts a BLOB-domain attribute to a character string in a text-domain attribute

to a BLOB view. Input is a character string. Output is a BLOB view.

INPUT: string DOMAIN: text

OUTPUT: output_blob DOMAIN: blob

FORMAT: textblob (blob)

Example:

The following code converts a character string to a BLOB:

SET <export blob view> TO textblob (<import char view>)

Functions - Numeric Functions in Action Diagram

The functions listed below are supplied numeric functions that let you add sophisticated

algorithms to the logic in action diagrams and action blocks. You use these functions to

manipulate numbers and to process dates and times. The numeric functions return values in

the Number domain.

Lengthblob

This function returns the length of a BLOB attribute. Input is a BLOB view.

INPUT: blob DOMAIN: BLOB

OUTPUT: blob_length DOMAIN: number

FORMAT: lengthblob(blob)

Limits: Up to 9 digits

Example:

The following example sets the output work length to the input of the lengthblob function:

SET output work length TO lengthblob(input work blob)

BLOB Functions in Action Diagram

The BLOB functions let you add algorithms to the logic in action diagrams and action blocks.

The following points must be considered while using the BLOB functions in an Action Diagram:

■ Avoid assigning a NULL value to either of the input BLOBs. The function exits with an invalid LOB handle error message.

■ When the length of the input BLOBs are zero, that is, the input BLOBs are empty, the function returns without any action.

CONCATBLOB The following point must be considered while using the CONCATBLOB function in an Action

Diagram:

■ If the concatenated length is greater than the length of destination, the output is truncated to available destination length.

SUBSTRBLOB The following points must be considered while using the SUBSTRBLOB function in an Action

Diagram:

■ If index is less than zero, the substring of the BLOB is from the zeroth index of the input BLOB.

■ If the length of the substring to be retrieved is less than zero, SUBSTRBLOB sets the length to zero.

■ If the length attribute given to the function is greater than the length of the BLOB, the output is truncated to hold BLOB until the end of BLOB.

Text Conversion Functions – BLOBDBCS, BLOBMBCS, BLOBTEXT, DBCSBLOB, MBCSBLOB, TEXTBLOB The following point must be considered while using the text conversion functions (BLOBDBCS,

BLOBMBCS, BLOBTEXT, DBCSBLOB, MBCSBLOB, TEXTBLOB) in an Action Diagram:

■ If the destination length is less than the length of input BLOB, the output is truncated to length of destination.

About the Toolset Completions String Manager Feature When an existing model is opened, the string properties in the model (.DAT files) may be converted to a

new format which allows the model to support up to half a million string properties. Once the .DAT files

are converted, an older release of the CA Gen 8.x toolset cannot read the new format although the

model may be uploaded and then downloaded to an older release of the 8.x toolset. A confirmation

message is displayed to allow you to decide whether to make that conversion now. Once the .DAT files

are converted, you will not receive this message again.

Previously, a toolset model allowed only 64K string properties to be stored locally.

Toolset Completions String Manager Feature Documentation

Context –Sensitive Help Topic in Toolset

Confirmation Message

When a model is opened for editing, the string identifiers in the model (.DAT files) are

converted to a new format which allows the model to support a maximum of half a million

strings (the earlier format that is allowed only 64K string properties). Once the .DAT files are

converted, an older release of the CA Gen 8.x toolset cannot read the new format.

This message gives you the opportunity to decide whether to make that conversion now. Once

the .DAT files are converted, you will not receive this message again.

Note: 8.x refers to the current release of CA Gen. For the current release number, see

the Release Notes.

Click one of the following options:

Yes—Specifies that the model (.DAT files) is saved in the new format and is then opened

for editing. After this, the model may not be opened with an older release of the CA Gen

8.x toolset. Once the model/subset has been converted, it may be uploaded to a Gen

encyclopedia and then downloaded to an older release of the CA Gen 8.x toolset.

No—Specifies that the model is not opened as this model is not upgraded to support

more than 64K strings.

Help—Describes the Confirmation Message dialog and its functions.

Messages in Gen Studio

Unable to Open the Model in CA Gen Studio

Unable to open the model in CA Gen Studio Reason: This error message is displayed while opening a model in Gen Studio. Solution: This model is not upgraded to handle more than 64K strings. To open this model in Gen Studio, upgrade the model in Toolset. Follow these steps:

1. Open the model in Toolset. It asks for a confirmation to upgrade the model.

2. Click Yes to confirm. The string identifiers in the model are converted to a new format which allows the model to support a maximum of half a million strings. The earlier format allowed only 64K string properties.

3. Close the model in the toolset and reopen it in Gen Studio. Note: An older release of toolset cannot read the converted .DAT files. To open a converted

model or subset in an older release of toolset, upload the model to a Gen encyclopedia and

then download the model to an older release of toolset.