User Guide
Service Parameters
To run the service, specify the source object storage and identify the input data set.
REQUIRED: "source"
Identify the transform source object storage, where the input resides. The source object storage details appear in the Model9 agent configuration file.
Required Keywords for "source"
Optional Keywords for "source"
OPTIONAL: "target"
Identify the transform target object storage. Values not specified will be taken from the "source" parameter.
REQUIRED: "input"
If you specify VSAM keywords for a sequential input data set, the transform will be performed and a warning message will be issued
Required Keywords for "input"
Optional Keywords for "input"
OPTIONAL: "output"
The output is the transformed data of the MF data set, accessible as S3 object
When transforming a file with the same name as an existing file in the target, the existing file will be replaced by the newly transformed file.
Note that the service does not delete previously transformed files but rather overwrites files with the same name, so when re-transforming a file using the "split" function, ensure to remove any previously transformed files to avoid having split files of different versions.
When splitting a file, wait for the successful completion of the transform function before continuing with the processing, to insure all the parts of a the file were created.
Specifying "text" format for a "binary" input will cause the transform to fail.
Service parameters samples
Transforming a plain text data set
Transform the latest backup of a plain text data set, charset IBM-1047, converted to UTF8 and compressed.
Transforming an unloaded DB2 table
Transform the latest backup of an unloaded DB2 table, charset IBM-1047, converted to UTF8 and compressed, located with a specific prefix:
Transforming a VSAM file using the defaults
When transforming a VSAM file, the defaults are a text key and binary data, transforming to a JSON output file:
Transforming a VSAM text file to CSV
Specify a text data, transforming to a CSV output file:
Transforming on Azure Storage using OAuth2
When transforming data on Azure blob storage with OAuth2 set the "api" to azureblob-oauth2 and use the azureOauth
section to specify Azure OAuth arguments as follows:
Table: Azure OAuth2 Arguments
Service response and log
The transform service is invoked as an HTTP request. It returns:
HTTP status
HTTP response
In case of a WARNING or an ERROR - the HTTP response will also contain log messages.
Informational messages are printed only to service log and not to the HTTP response. The service log can be viewed on the AWS console when executing the service from AWS, or the docker log, when executing the service on-premises.
Log
Service response and log samples
Status OK sample
Status WARNING sample
Status ERROR sample
Input format support
Supported formats
SMS-managed data sets
Non-SMS managed data sets
Sequential and extended-sequential data sets with the following RECFM:
V
VB
F
FB
FBA
Non-extended VSAM KSDS data sets
Unsupported formats
RRDS, VRRDS, LINEAR, ESDS
Extended format data sets with compression or encryption
PDS data sets
RECFM not mentioned above (U)
Output format support
Text
JSON
CSV
DB2 Image Copy Transform Guide
Configuration
Make sure that
<M9_HOME>/scripts/transform-service.sh
has execute permissions. If not, add it by usingchmod a+x <M9_HOME>/scripts/transform-service.sh
.Copy
M9XFDB2
from Model9's SAMPLIB data set to a PDS data set of your choosing.Edit
M9XFDB2
and replace the placeholders enclosed with angle brackets with the following:
Table: Placeholders
Replace the remaining placeholders in the JCL as described in this manual.
Execute and verify results
When done, submit the job and make sure it ends with MAXCC of 0.
Via SDSF, verify that the transform service was in fact called and completed successfully. Successful output would look something like this:
Supported DB2 Column Types
Table 5. Supported DB2 Column Types for Transformation
Last updated