Release Notes Version

(1)

Release Notes

Version 10.06.12

(2)

Page n°2/20

: DB2 PTF group for free-form RPG with embedded SQL.

(7)

Page n°7/20 SI51094:

for free-form RPG with H, F, D, P specifications.

If less (V7R1 without PTF SI51094, V6R1 or V5R4): possible, but only C specifications will be converted.

ARCAD plug-ins version and Client Applications

It is mandatory to update your plug-ins and RCP applications to the version 10.01.00.

Note that your plug-ins and RCP applications version 08.xx.xx are not compliant with ARCAD Server v 10.06.xx.

ARCAD version level on remote sites

It’s better (and more simple) if the sites that you are using for classic distribution are also migrated to ARCAD 10.06.xx at the same time.

But, using special processes in your macro, you can run a previous version of ARCAD on your sites, allowing you a progressive migration of ARCAD versions on the remote sites.

However, migration to ARCAD 10.06.xx is mandatory if you are using these systems with ARCAD- Extract or ARCAD- Deliver (distribution to extended environment).

Version installation

It's not possible to install the version 10.06.12 as a cumulative to upgrade an ARCAD version 08.xx.xx.

ARCAD migration procedures (Recovery)

You must do an installation using a “Cancel and Replace” method, if your current level is between 08.06.00 and 08.xx.xx.

If your current version level is less than 08.06.00, you must first install a cumulative to 08.1x.xx.

An audit should be done on your V8 Arcad installation, before installation for migration to V9.

It is also advisable to install (temporarily) a V9 instance of Arcad, just to test the migration process duration (but you can normally continue to use your Arcad V8 in parallel).

Please contact Arcad support for more information about this.

Please refer to the "ARCAD Installation" part of the "Major Enhancements in this version" chapter in the “Release Notes - version 09.01.00” document.

MODIFICATIONS IN STANDARD MACRO-COMMANDS

If your current level is lower than 09.01.00, please refer to the Release Notes of the version 09.01.00

OTHER IMPACTS

None if your current level is equal to or higher than 09.01.00. If not, please refer to the Release Notes of the version 09.01.00

(8)

Page n°8/20 MAJOR ENHANCEMENTS IN THIS VERSION

ARCAD-OPEN REPOSITORY/PROCESS &LIST MANAGER Macro-commands

Use of new variables in the macro-commands for the submit jobs.

Three new variables are available in the macro-commands for identifying the last submitted job:

ASBMJOBNAM (*NAME 10) Last submit job name ASBMJOBUSR (*NAME 10) Last submit job user ASBMJOBNBR (*NAME 06) Last submit job number

ATFROBJ: Transfer objects

Possible problem in ATFROBJ and other commands when the default value for CRTDUPOBJ CST() command parameter has been changed to CST(*NO).

A modification has been done in several ARCAD programs in order to avoid problems with constraints for some processes (such as ATFROBJ) when CRTDUPOBJ does not have the default value *YES for parameter CST().

Remark: it's not a good idea to change parameters such as this in the CRTDUPOBJ command, as it could impact many software packages!

Removal of %LOC in source members

ATFROBJ: Transfer objects + ATFRSRC: Transfer source members:

When transferring a source member, the %LOC keyword is inserted into the source in order to manage the localization.

However, in some cases, the keyword should not remain in the member.

The RMVLOCAT parameter (Remove the localization) has been added to the ATFROBJ and ATFRSRC commands to allow the removal of the %LOC keyword from the source when necessary.

ADSPAPPVER: Display Application Versions Display the indentation for the incremental versions

With the ADSPAPPVER command, the incremental versions can be displayed with an indentation so as to see the different levels better.

However, when the level was too high the version number was not displayed.

This problem has been corrected.

Now, when the level is too high the version number is displayed aligned on the right and preceded with "..." to indicate that the indentation cannot be fully displayed.

ACRTIFSLST: Create a list of IFS directory objects Retrieve the object data size in the IFS object lists.

In the IFS objects lists it's now possible to retrieve the size of the objects data using the keyword

*DTASIZ.

The keyword *OBJSIZ, already in use, retrieves the allocated size of each object.

ASCNRPLCLP: Scan/Replace CL keyword values

New command to add or modify command keywords and corresponding values in a CL program.

The ASCNRPLCLP command adds or changes keywords and values for commands in one or more CL programs (CLP or CLLE) by creating output source members.

(9)

Page n°9/20 AEDTMACCMD: Edit a macro command

Use of new variables in the macro-commands for the sequences processed in batch

In a macro-command when we want to process a sequence in batch, it's now possible to use variables for the job name, the submission JOBD and its library.

All ARCAD modules

Conversion to /Free form for ARCAD (SQL)RPGLE programs.

From version 10.04.00 and higher versions, we convert all the modified (SQL)RPGLE to /Free form syntax, using the ACVTRPGFRE command.

More than 400 RPGLE programs were converted in version 10.04.00.

There is no impact on the execution of these programs.

ARCAD-SKIPPER 5250

Various Skipper unitary commands

Execute specific macro-commands (pre-check and post-execution) on various Skipper unitary commands

On various Skipper commands it is possible to execute a macro-command, either:

- before the process with parameter CHKMACRO (default value *NONE) - if the macro-command ends in error, a message is sent and the process is terminated; or

- after the process with parameter INITMACRO (default value *NONE).

The macro-commands must exist in the current library list (*LIBL).

The type and the parameters of the macro-commands are described in the online help for each command.

The relevant commands are:

ACHKOBJOUT ACHKOBJIN AADDSRCARC AADDOBJARC ADLTOBJARC ARNMOBJARC ATFROBJARC ARMVOBJARC ACHGOBJTYP ACHGOBJLOC ATFRTOTST ATFRFMTST

ARMVOBJARC: Delete component modifications

Enhancement to remove-component function: Add option SAVESRCMBR - save or do not save source member(s).

The ARMVOBJARC command automatically saves the source member of a component.

Now, it's possible to specify that you don't want to save it using parameter SAVESRCMBR.

ADLTVER: Delete a version

ADLTVER doesn't remove the merge from the component record and LSTMRG list.

If a component is in more than one active version, a version check (ACRTVERLST) flags it so that changes can be merged.

If the version was deleted, this indication was not removed.

The problem has been corrected - the merge information is now removed for the deleted version.

(10)

Page n°10/20 ARCAD-SKIPPER PLUGINS OR RICH CLIENT

Component Management

Display a notification when a job submitted from Skipper end abnormally

A dialog box is now displayed when a job submitted from Skipper (macro jobs, version control, compilations, etc.) ends abnormally.

For example, if the job is ended using the ENDJOB command from an emulator session, then the notification will be triggered.

Layout revamped for properties - Application Authorizations.

The application authorizations list (properties) has been rearranged in groups to improve readability.

ARCAD-TRANSFORMER DB

ACVTDDSSQL: Convert DDS file to SQL

Field ranking for a Logical file converted to an INDEX.

When a logical file with a format different to the physical is converted to an INDEX, the key fields are not included because they are implicit, and the others are ranked in the logical file order.

A message indicates this format change.

ARCAD-VERIFIER Service Providers

ARCAD-Verifier Start and Stop Service Provider.

It is now possible to use the Start and Stop capture and execution Service Providers.

The Start and the Stop are launched in 2 different calls. Stop takes the scenario id and the new result id as parameters (provided by the Start).

Please refer to Service Provider documentation.

Campaign management Campaign without function

It is now possible to generate campaigns without considering their scenario's functions. This choice can be made at the generation or defined in a preference.

Campaign Execution

Results from a campaign execution as reference (default)

All results from a campaign execution can be set as reference (default) via contextual menu.

Campaign Execution / Comparison Report Comparison report from campaign execution

All comparison reports from a campaign execution can be generated via contextual menu.

(11)

Page n°11/20 MOST IMPORTANT CORRECTIONS IN THIS VERSION

ARCAD-OPEN REPOSITORY /PROCESS &LIST MANAGER AUPDXRF: Cross-reference update

Error in cross-reference update for large number of components (DECLARE3).

Sometimes, when processing a large number of components (for example, when loading a new application using DECLARE3), an error occurred (MCH1210/RNQ0103).

ADSPTFRLOG: Display transfer log

History for some IFS components not shown.

Some IFS components were not shown on the Transfer Log, using AWRKOBJARC option 50 (ADSPTFRLOG).

ACHKOBJTKN: Check held tokens

In ARCAD V10 token reference for component not updated.

There was a problem affecting the search and extraction of java components that have taken the token in a version in V10.

ACVTLSTFMT: Convert a list from V8 to V10 format Copy-list failed for list converted from V8.

The change-date in list entries in ARCAD V8 were prefixed with "20" (century) even when the date was blank.

This caused an "invalid date" (CPD0082) error when a list converted to V9 or V10 was copied.

ADSPDDSIMG: Display DSPF/PRTF image Error when testing display.

Using option 10 from the AWRKOBJARC components list to "execute" a display file sometimes failed.

AWRKLST: Work with lists

Impossible to work with more than 9999 lists.

The command AWRKLST doesn't allow you to work with more than 9999 lists.

An error occurred in this case.

Now a message indicates "Maximum capacity reached for subfile.".

It is possible to reduce the number of lists displayed by specifying a library name, a specific list name or a generic name.

(12)

Page n°12/20 ASAVMACCMD: Backup macro

Problems with Macro Save and Restore.

1. Error was correctly flagged when the DEV (device) parameter was not entered.

2. If the macro was not in the SYSBAS ASP, it was not restored at the target.

These problems have been corrected.

ACMPLST: Compare two lists

List compare failed for selection field 1.

When comparing 2 lists, specifying selection-field 1 with any other operand than *NE, there were no records selected.

ACPLOBJ: Compilation

SQL RPG service program with bound module failed compilation after 1st compile.

When one or more modules were added automatically for an SQL RPG Service Program, for example due to a binding directory specified in the control (H) specification, subsequent compiles failed due to an error on the generated compile command (BNDDIR parameter).

Data area compile not rolled back.

It was not possible to roll-back the "compile" of a data area in ARCAD, because the saved object was lost (library ARRPLOBJ).

This problem has been corrected - the "old" data area component can now be recovered using the roll-back function/command.

Problem re-using component names that were deleted from the repository.

Environment transfers with compile failed if a component was incorrectly added to the repository, deleted and the same name then used for another type or source with/without object.

Compile with trigger fails for library outside of ARCAD.

An error occurred when compiling a file with a trigger in a library that is not part of an ARCAD application.

AEDTAPPCPT: Work with component types

Objects types not displayed when working with component types.

When we displayed the components types for an application, the object types were displayed.

However, when we displayed all the types (F11=All types) the objects types were not displayed.

ATFROBJ: Transfer objects

Transfer trigger fails after initial transfer.

There was an error when recreating triggers in an environment during a transfer or using ACPLOBJ, if there was more than one trigger with the same name (eg. for *INSERT and *UPDATE).

AGENFILSRC: Extract the source for a file

Logical file source generated with DYNSLT keyword erroneously.

When the source was extracted using AGENFILSRC for a logical file having select criteria, the DYNSLT (dynamic-select) key word was included in the source, even when this was not in the file definition.

(13)

Page n°13/20

This sometimes happened during a file transfer (ATFROBJ command).

The problem has been corrected.

ACPLOBJ: Compile a component

Compilation error for service programs with activation deferred

There was a compilation error when we compiled a service program (ILESRVPGM) that had links with a service program with "Deferred activation", eg: with BNDSRVPGM((... *DEFER) (...*IMMED)) specified.

ACVTARCDBF: Convert ARCAD DB from V8

After upgrade from V8, the AARKUSRF1 had duplicated profiles.

In V8 it was possible to have 2 user entries with the same user profile specified.

There was no check in the conversion process to ensure that the user profile was unique within the list of users (I_ARCAD) in V10.

AEXCLST: Execute a command for a list

Execute command in list: syntax error causes program error.

If an incorrect replacement value was added in the AEXCLST command CMDRPL() parameter, there was a program error which generated a dump.

This problem has been corrected - a standard syntax message is now issued.

AWRKSRCTYP: Work with source types

Erroneous addition of %LOC in source caused by AWRKSRCTYP.

The ARCAD instruction %LOC is automatically inserted into the source of a component if the

"Insertion %LOC in the source" option is set for a particular Source Type (see AWRKSRCTYP command or option 11 on the I_ARCAD menu) or if the source file is set to *MERGE data management (see ASETDTAMNG command).

This instruction is added as a "comment" line, using the character(s) and position specified with the AWRKSRCTYP (option 2, 2nd page).

These values must be entered when the "Generation of header cartridge" option is set to "Y".

However, when set to "N", the "Starting comment characters" value was set blanks, even though it is used for the %LOC instruction.

This problem has been corrected. The "comment" characters are no longer set to blanks.

AGENSQLSRC: Generate SQL source for an SQL Object

SQL source record-format name changed when identical to the short (system) file name.

When the record-format name for an SQL table was the same as the short (system) name, the file/table created from the generated source had a record-format name based on the long (SQL) table name, instead of the short (SYSTEM) name.

AEDTMACCMD: Edit a macro command Character search in a macro-command failed.

Searching characters in a macro-command sometimes failed with MCH1210 (Receiver value too small to hold result).

(14)

Page n°14/20 ARCAD-OPEN REPOSITORY/KNOWLEDGE BASE

AUPDXRF: Cross-reference update Cross-reference update failed for a TABLE.

During the cross-reference calculation for a TABLE the data type NVARCHAR was not recognized and caused errors.

Cross-references not calculated for IFS source with more than 1000 lines.

Since version 09.00.20 of ARCAD, an error occurred:

When an IFS source had more than 1000 lines, the cross-reference calculation ended with no result.

Cross-reference error for RPGLE Free, for "exported" procedures.

An error was introduced in version 10.06.04:

When an RPGLE source uses Free syntax (Column 8-80, or Fully-Free) for the declaration of the ILE procedures, these procedures were not seen as "Exported", even when the "Export" key word exists on the 'Dcl-Proc' line.

Due to this error, it was not possible to interrogate the "Calling chain", at procedure level, when the procedures are in *SRVPGM.

This problem has been corrected, but the incorrect cross-references must be recalculated.

RPGLE cross-references: Invalid line for labels or fields present on an ENDSR line.

In RPGLE, we may have a label (tag) on the ENDSR instruction.

We may also have a field in the ENDSR line for the *PSSR subroutine.

In the cross-reference, the lines for these fields were incorrect - the BEGSR lines were retrieved instead of the ENDSR lines.

Some exported procedures omitted from the cross-reference.

If the source for an exported procedure had statements between the begin-procedure and procedure-interface statements, the EXPORT keyword was not recognized, so did not show as exported in the procedure cross-reference.

Invalid cross-reference when a TABLE or SQLPRC uses an SQLUDT.

When a TABLE or a SQLPRC defines a field using a UDT type, the ARCAD cross-references were incorrect.

Attention: the link between TABLE or SQLPRC and SQLUDT is visible only when we ask for the

"program".

ADLTENV/ARNMENV: Delete/Rename an environment Rights to delete or rename an environment.

A user could delete or rename an environment even with no rights to manage the associated application.

Now a user must be authorized to manage the application in order to delete or rename an environment.

ADSPXRF: Display cross-references Overflow on the cross-references screens.

The programs displaying the cross-references can manage a limited number of records (often 9999, but sometimes less).

(15)

Page n°15/20 When the number of records was too high there was a crash.

Now a message indicates "Maximum capacity reached for subfile.".

Sometimes, but not always, it's possible to display the following records using "Starting from".

ACRTSXRLST: Create a list based on source cross-reference

Error comparing RPGLE prototypes when they are in Free syntax or Fully-Free syntax.

When we edit a source member containing an RPGLE Copy clause, or when we do the ACRTVERLST for a version where such copy clauses exist, the following problems could occur:

- When the Copy clauses use Free syntax, in column 8-80 for the prototypes, the "requirement" to recompile was not always correct;

- When the Copy clauses use Fully-Free syntax, in column 1-xxx for the prototypes, an error could occur (module AARD294M2).

These problems have been corrected.

ARCAD-OPEN REPOSITORY/DATACHANGER AWRKDTCTYP: Work with DTC types

Help text corrected for DTC type Post-transfer exit program.

For a DTC type it is possible to specify a "Post-transfer exit program" to be called after DTC objects of this type are transferred, using the AWRKDTCTYP (option 2).

The description of the parameters for this program were wrong, but have now been corrected.

ARCAD-SKIPPER 5250

AWRKOBJARC: Work with ARCAD components

Insert system function tree in source text: version number added multiple times.

When the application option "Insert version number in source text" was set to Y, the version number was added to the component text for every update to the source, resulting in the version appearing multiple times in the description.

ACHGAPPLBL: Apply application library list to current job Error initializing an environment/version.

There was an error in the ACHGAPPLBL command (used when initializing an environment ((AINZCURENV command) when a system library (specified in the System value QSYSLIBL) was also the current library.

ARNMVER: Rename version

Rename failed with lists in V8 format.

It is possible that a version contains lists in V8 format after conversion to V10.

In this case, the rename-version operation did not process those lists, causing errors.

ARNMVER loses the merge information from the component record.

If a component is in more than one active version, a version check (ACRTVERLST) flags it so that changes can be merged.

When a version is renamed the component merge information is reset, with the assumption that is will be updated by the next version check.

However, this check only takes into account versions that are still open. So, if a merge is still outstanding from a version that has been closed, the check-flag is lost.

(16)

Page n°16/20

This problem has been corrected. The component merge information is only removed if the new version number is less than that of the version to be merged, which will not happen when the version to be merged has been put into production.

ATFROBJARC: Transfer a component to another version

Document links: change of component type followed by move to another version.

When a component had its type changed at *VERSION level, then was moved to a different version, there was still a document link for the old component type to the old version.

ARCAD-SKIPPER PLUGINS OR RICH CLIENT Component Management

DDS visualization screen not working.

In the Skipper Plugin, the DDS visualization editor failed.

Component Version History view shows only the base version.

Skipper Client Component Version History view showed only the base version for a component.

Check-out fails from the Version Log view.

The check-out of a component from the Versions Log failed due to a bad parameter passed to the ACHKOBJOUT command.

Copied component disappears from the Version components view.

When a component was copied from one version to another by using the "Move" action and then selecting "Copy" as move action, the component disappeared from the Version components view.

Option labels and icons disappear from the component context menu.

After several requests to display the component version history, the option labels and icons were sometimes no longer displayed in the component contextual pop-up menu.

Component source display from Cross-reference Calls view.

Components listed in the cross-reference "Calls" view were affected by a problem preventing their sources from being opened.

Connection's CCSID not restored properly in dialog combo box.

The preselected CCSID in the connection dialog combo box was the first one matching the previous user CCSID code, but not necessarily its description.

Components not saved after LPEX restoration.

When the LPEX editor was restored (after closing RDi with the editor left open and restarting RDi), the editor could be closed automatically under certain circumstances, and component modifications were lost.

This problem has been corrected - it's now possible to save before the editor is closed.

(17)

Page n°17/20 Improvements to Component Duplication wizard.

The component duplication wizard has been improved to add the capability to select if the duplicated component must be linked to its reference component and to allow the selection of a target version if Skipper is not already initialized in a version.

Unable to compare a component with one of its versions.

It was not possible to use the plugin comparison features as the selection of the component version- to-compare to was not possible.

Error when during a version control/check.

When launching a "version control" to check the integrity of a version, an error may be displayed saying that a problem occurred during the check process.

On the IBM i, the check/control is correctly executed but the results are not retrieved and displayed correctly.

Deleted versions don't appear as deleted in the components' version history.

In the component history log, deleted versions did not appear as deleted in the list.

Their description was still displayed as any other version.

This description now shows as "Deleted version" and they are easily seen in the list as their background is displayed in black.

Skipper client

User profile gets disabled after Eclipse's start

Skipper client could sometimes try to connect to a remote system using a blank password, leading to the profile being disabled.

IFS files incorrectly retrieved from remote system

IFS files could sometimes be retrieved using the wrong method.

ARCAD-DELIVER EXTENSIONS FOR RTC Build Definition

Invalid value of the Macro-Command “Failure Message Id. List” field

The content of the “Failure Message Id. List” sometimes contains the value of the “User Data Filter”

field.

The problem has been corrected

ARCAD-OBSERVER /DOCUMENTER Documenter generation and export

Maintenance report subchapter fails to generate if the component table is displayed.

A problem was preventing the Maintenance Report subchapter from being generated if the Maintenance Report components table was to be generated as well.

Documentation export to a single file fails.

A dependency problem occurred during the exportation of the documentation in a single file.

(18)

Page n°18/20

Documenter: versions list is empty if environment code is not D.

When importing versions to be documented using the Observer plug-in, the version importation wizard's combo-boxes were empty if the target application had no environment with the code D.

ARCAD-TRANSFORMER RPG(FREE CONVERTER) ACVTRPGFRE: Convert RPGLE to Free form

The comments located on column 1-5 and 81-120 are lost for some converted instructions.

When comments are in columns 1-5 or in columns 81-120 of the C-specifications of the source to convert, these comments are lost in the converted source in the following cases:

- When the conversion of one C-Spec instruction needs several lines in Free form - no comment on the added lines;

- Special conversion for replacement of KLIST key lists, when the key fields are moved directly to the Chain/Read/... instruction;

- Special conversion for replacement of CALL+PARM to a prototyped call;

- Special conversion for the management of GOTO/TAG instructions.

Now, most of the converted C-Specs keep the comments that are in columns 1-5 and columns 81- 120, when the conversion is requested using FLGCVTTYPE(*KEEP).

Note: the default is FLGCVTTYPE(*NO).

Invalid conversion of an IFxx or DOWxx with ANDxx or ORxx, when 'SR' is present in column 7-8.

An error occurred on conversion of IFxx or DOWxx instructions when 'SR' was in column 7-8 for the ANDxx or ORxx lines:

Example :

* The original source is : CSR *IN52 IFEQ '0' CSR TRANS ANDGE BEGYMD CSR *IN52 DOUEQ '1' CSR TRANS ORLT BEGYMD

* Converted source : If *IN52 = '0';

and TRANS >= BEGYMD;

DoU *IN52 = '1';

or TRANS < BEGYMD;

The ';' was added at the end of each line, instead of the end of each instruction.

Instruction for a CABxx is lost, when it is followed by CASxx and the corresponding TAG.

When the source to convert contained CABxx instructions followed by a group of CASxx.. ENDCS instructions, then followed by the corresponding TAG, with no other kinds of instructions between the CABxx and the TAG, there was an error in the converted source: "No instruction is present for the CABxx instruction".

Error message in the conversion, when '/Free' exists in the source after column 7.

The source to convert can contain '/Free' clauses that are not at position 7, but 8 or higher.

This is possible only since the V7R2 - or V7R1 TR9 - RPG compiler level (and these clauses are ignored by the compiler).

However, in that case, escape messages were often issued during the conversion.

Error for usage of L0 indicator in C-Specification.

An old RPG program could use the special indicator L0 in column 7-8.

(19)

Page n°19/20

In this case, the converted source had an error - it tried to use *INL0, which does not exist.

Invalid field name pXToArrStr for conversion of a MOVEA instruction.

The conversion uses special variables AToArrStr, pAToArrStr to manage a MOVEA instruction in Free syntax.

However, a problem occurred when one of the 2 variables was a Data Structure - the name of the generated variables were wrong.

ARCAD-TRANSFORMER DB

ACHKFILDTA: Check file data integrity Transformer DB: Wrong library list.

When we submitted a check file data integrity (using SBMJOB) in mode *BATCH with *LIBL,

*ENVOPELIB or *ENVLIBL the library list was not correct.

ARCAD-VERIFIER

ARCAD command interception - CRTDUPOBJ: (Create Duplicate Object) Regression: CRTDUPOBJ command interception - recursive call setting triggers.

A regression occurred in version 10.06.03 for the ARCAD command interception of CRTDUPOBJ, causing a recursive call error when setting triggers.

Verifier Cross-references

Missing cross-reference information.

When a PEX trace is used to collect the job trace information for many object accesses in a scenario, the storage size may not be sufficient and information then lost.

A new server parameter allows the management of this storage size.

Verifier context management Limited number of libraries.

The creation of IBM i data context or BATCH or INTER application context had an error when the number of libraries was greater than 14.

Comparison template

Comparison template not used

The comparison template is now used even if results compared have been executed, both, on dedicated context.

Campaign management

Adding manually a scenario to a campaign

A control has been added. All scenarios in a campaign should have same engine.

(20)

Page n°20/20 APPENDIX

ARCAD CUMULATIVE STANDARD INSTALLATION INSTRUCTIONS

Use this procedure to apply version 10.06.12 cumulative updates to an IBM i server that is currently running ARCAD.

To restore the cumulative from the tape/CD while retaining all the applications that are declared on your system, please follow the steps below:

1. Connect to the QSECOFR profile.

2. CHECK THAT NO OTHER USERS ARE CURRENTLY USING ARCAD, using the following operating system commands:

WRKOBJLCK ARCAD_PRD *LIB

WRKOBJLCK ARCAD_PRD/ARCPLSRC *FILE

3. Insert the tape/CD and enter:

LODRUN DEV(TAPxx or OPTxx).

If no errors occur during the upgrade of ARCAD, do not forget to close the session (SIGNOFF).

Once complete, you can start working with ARCAD again.

Release Notes Version

Release Notes

Version 10.06.12

TABLE OF CONTENTS

: DB2 PTF group for free-form RPG with embedded SQL.

for free-form RPG with H, F, D, P specifications.