This menu holds all of the system values which control the behavior of Data Cases.
General Settings
The following options relate to remote data extraction only.
Remote User Profile When a remote Data Case is maintained or executed a connection has to be made to the remote system. The default option is to use the User Profile for the current session to connect to the remote system. The alternative is to set up a standard User Profile on this screen which will be used for all remote database connections. This Profile must have ‘Limit capabilities’ option set to *No.
Remote User Password The password for the above user profile. If left blank the password is assumed to be the same as the profile name. The standard, default length is 10 characters.
If your IBM system value is set to accommodate longer passwords,
as of TestBench 8.2.0, up to 128 characters for the FTP password is supported.
The TestBench screens for the password entry will change based on which password level is specified for the IBM system value QPWDLVL.
Last Unique Remote Extract Lib
This is incremented automatically by TestBench and should not need to be changed.
Reserved SQL Keywords
If you are using the data extraction functionality in TestBench and the field names on your files are the same as any of the SQL reserved keywords (eg. DATE, YEAR, FROM) this option should be set to ‘1’. TestBench will then search for these keywords and enclose field names in quotes before executing any SQL statements. If you leave this option as ‘2’ and during an extraction a field name is found that is equal to an SQL keyword, the extraction will stop and a message will be placed in the job log.
Send Message for Media Extract
When using the Media method to transfer data between machines, once the data is extracted on the remote system the status of the Data Run changes to ‘MedReady’. Setting this option to a ‘1’ will cause a message to be sent to the designated message queue informing that the library of extracted data is ready to be transferred to the local iSeries, after which point an option ‘13’ on the Work With Data Runs will resume the extract process.
Media Extract Message Queue
This should only be used if the above option is set to ‘1’. It is the name and location of the message queue to which the message should be sent indicating that the extracted data is ready to be transferred to the local machine.
Use Secure FTP for Remote Data
This option was introduced in version 8.0.0.
With this option set to a 1 Yes, secure FTP (FTPS) will be utilized to transfer remote data.
With this option set to 2 No (default), then standard FTP will be used to transfer remote data.
Template
Create the default settings for all new Data Case Descriptions, which can be overridden at creation time for each Data Case.
Remote System Definition
For remote data extractions we need to know the name of the library on the remote system which contains the extraction functionality, e.g. TB_7PO, EX_7PO. Default values can be set up using this option which are displayed and can also be modified when a remote data case maintained or executed. If the remote library name is entered or changed at maintenance or execution time an entry will automatically be added to this panel.
Remote Database The name of the Relational Database to extract data from.
Product Library The name of the library on the remote system which contains the extraction functionality, e.g. TB_7PO, EX_7PO. If specified this library will be used as the default when a connection is made to the remote database. If no entries are made here the default value will be the name of the product library on the local system.
Run Priority The run priority that will be applied to the extract job on the remote machine. The original setting is re-applied after the job completes.
Timeslice The timeslice that will be applied to the extract job on the remote machine. The original setting is re-applied after the job completes.
SQL Error Code Exceptions
When a Data Case is executed, a warning is created if an SQL error is generated as part of the run. However, some error messages may be acceptable and therefore this option enables exceptions to be set up. Any SQL error messages defined here will not cause a Data Case warning to be generated.
4 – Delete Remove the SQL error code from the list. A confirmation screen is displayed prior to the deletion taking place.
F6 – Add Add a new SQL error code exception. A new window is displayed into which the code can be keyed. The code is validated so that an invalid code cannot be entered.
Define Unique Key
As of TestBench version 8.3.0, support has been added for unkeyed files.
For data extraction, TestBench adds primary keys to SQL selects to avoid duplicate records in the target library.
In the rare occurrence of files with no primary key, a duplicate record attempt can occur for two scenarios:
- Data Case defined with Data Option of *ADD
and - Data Cases with the same file defined more than once.
To resolve this challenge in this unique occurrence, TestBench now provides an option to
define a unique key for files.
To resolve this challenge in this unique occurrence, TestBench now provides an option to define a unique key for files. To find this feature, from the main menu, select Utilities and System Setup option, followed by Data Case System Options.
In the Define Unique Key menu option, there is a Unique Key Definition screen where the user can add/remove files. When defining a file, the user specifies the file name, and a library.
For the library field, either a specific, existing library name or *ANY can be defined.
Note, for *ANY, the file must be found in the library list.
Once a file is entered, there is a Compare Key Definition screen where a user can specify numeric values for Key Sequence column for the field(s). TestBench will effectively treat the field(s) that have a sequence number specified for the Key Sequence column as a unique key(s) during the data extraction.
