Additional data are using two tables with identical table structure – twaz_addata, twaz_addata_hist.

Table Twaz_addata stores additional data for actual, modified, inserted tws app records.

Twaz_addata_hist stores additional data for history, interim tws app records.

Structure of both tables

The structure of IWS additional data is defined in XML files. The XML files have 2 different formats – wai format and JCL format. The format is configured by process config setting addata_format.

Wai format is default XML format. This XML format is used for configuration of form and items that are stored in it. XML files are configuring input dialogue for fields that can be stored in additional data. The XML files are placed to directory etc/addata of ProcMan installation directory.

Example of XML file in wai format:

<?xml version="1.0" encoding="UTF-8"?>
<form action="" name="twaz_ad_addata" method="post" id="twaz_ad_addata" remember="false">
	<!--example note 1, that shows textbox 80 characters long-->
	<fi key="note1" type="text" name="note1" maxlength="80" translate="false" heading="Note 1" help="Help for note 1" remember="true"></fi>
	<!--example note 2, that shows text area -->
	<fi key="note2" type="textarea" name="note2" rows="10" cols="70" maxlength="100" translate="false" heading="Note 2 heading" help="Help for note 2" remember="true"></fi>
	<!--example checkbox 3, that shows check box -->
	<fi key="checkbox3" type="checkbox" name="checkbox3" translate="false" heading="Add operation" help="Add operation help" remember="true"></fi>
	<!--example select 3, that shows simple select true/false -->
	<fi key="select4" type="select" name="select4" heading="Test select" translate="false" remember="true" help="select true or false">
		<val heading="true">1</val>
		<val heading="false">0</val>
	</fi>
</form>

JCL format is XML format that is used also for entering JCL user data. Detailed description of this format you can find in chapter 6 of document “ProcMan - Customization JCL Module”. The files are stored in directory etc/forms.

Additional data are configurable customer’s data used in IWS handover that are connected to iws applications or operations. These data are stored only in ProcMan database but not in data structures of IBM Workload scheduler on z/OS.

IWS additional data that are not integral part of IWS data and they are not accessible on z/OS.

Structure of IWS additional data is configurable to suit needs of certain handover process.

Configuration of data structure is done using XML files see chapter 6.2.

The default IWS additional data configuration is stored in etc/hos_tws_config.php file. It contains setting addata_conf, addata_editor.

The addata_conf setting is array list. The list can contain two keys.

• Key adcom defines XML configuration file used for edit and display additional data connected to common segment (adcom).

• Key adop defines XML configuration used for edit and display additional data connected to operation segment (adop).

The addata_editor setting is array list. This setting is applied only to JCL format and is configuring Codemirror editor, which is used for Additional data value editing. Array key is filter to additional data key. Array value is Codemirror editor keyword.

Example for editing with XML mode all additional data containing TWSRULEAPP

$addata_editor['TWSRULEAPP:'] = "XML";

To customize the certain handover process default configuration can be overwritten by PHP process definition file.

The interfaces of modules that can display or edit additional data have configuration settings addata_conf, addata_format, addata_edit.

The addata_conf setting is array list. The list can contain two keys.

• Key adcom defines XML configuration file used for edit and display additional data connected to common segment (adcom).

• Key adop defines XML configuration used for edit and display additional data connected to operation segment (adop).

The addata_format setting is array list. The list can contain two keys.

• Key adcom defines XML file format used for edit and display additional data connected to common segment (adcom). Possible values are wai or jcl.

• Key adop defines XML file format used for edit and display additional data connected to operation segment (adop). Possible values are wai or jcl.

The interfaces of modules that can display or edit additional data have configuration option addata_edit. This setting will enable (addata_edit=true) or disable (addata_edit=false) editing of additional data. The default setting for addata_edit is false, so without setting addata_edit option additional data will be read only.

Example: This configuration list use XML file addata_example.xml to configure additional data in common segment, XML file twsmod_adop.xml to configure additional data in operations segment

addata_conf = [adcom = "addata_example",adop = "twsmod_adop"] , addata_format=[adcom = "jcl",adop = "wai"], addata_edit=true

-h show help menu

-o option for manipulation - import, export

-s IWS data segment – adcom (applications) or adop (operations), default value adcom

-f Filename for command ouput or input

-c csv file format, txt or excel, default txt, txt is csv format for common text editors, excel means csv format readable by MS Excel, the main format differences are in multiline text fields

-e text encoding of csv file, UTF-8 or CP1252 (Windows-1252), default UTF-8

-m file export mode, w - overwrite existing file, a - append existing file

-i export filter, option for exporting only part of IWS applications, consisting from pairs of name=value separated by semicolons, example adid=AD*;subsys=TWGC – filter for all applications starting with AD from system TWGC,

The export filter can use following fields:

adid - Application ID

subsys - IWS system

Owner - Application owner

type - Type

stat - Status

authgrp - Group Definition

grpdef - IWS Authority group id

addname - Additional data field name

dbstat - State (ACTUAL, INSERTED, MODIFIED)

tws_addata -o export -s adcom -f export.csv -- export additional data in common segment to file export.csv

tws_addata -o export -s adop -f export_oper.csv -- export additional data in operation segment to file export_oper.csv

tws_addata -o import -s adcom -f export.csv -- import additional data from file export.csv to additional data in common segment

tws_addata -o import -s adop -f export_oper.csv -- import additional data from file export.csv to additional data in operation segment

tws_addata –o export –s adcom –i adid=BG*;owner=P368V – export all applications with id starts with BG, owner of application is P368V

IWS additional data can imported or exported to text based csv files. Import and export is done using the batch file tws_addata.cmd, which is located in the bin directory in ProcMan installation.

The command is using for export and import of data csv format (comma separated text). csv file consists from 3 common fields and 1 optional field:

• application key – application key for tws application

• operation number – optional field operation number for operation data for operations

• field name – field name of additional data

• field value – field value of additional data

The csv file is by default in character encoding UTF-8, but it is possible to use also character encoding Windows-1252.

Example of csv file with IWS additional data

application key, field name, field value

application key, field name, field value
"ACTUAL.TWEC.BGT3000A.P.A.20711231","note1","test1"
"ACTUAL.TWEC.BGT3000A.P.A.20711231","note2","test 2 \n test22"
"ACTUAL.TWEC.BGT3000A.P.A.20711231","select4","1"
"ACTUAL.TWEC.BGT3001A.P.A.20711231","checkbox3",""
"ACTUAL.TWEC.BGT3001A.P.A.20711231","note1","test 1"
"ACTUAL.TWEC.BGT3001A.P.A.20711231","note2","test 2"
"ACTUAL.TWEC.BGT3001A.P.A.20711231","select4","1"