release notes - version 10.08 - arcad software

RELEASE NOTES Version 10.08.02

Publication Date: 12/01/2017

Document: Release Notes

Created by: R&D

Date: 10/05/2017

Edition/Revision: 1/0 Status: Released

Release Notes

Version 10.08.02




Created by: R&D

Date: 10/05/2017


Page n°2/32

TABLE OF CONTENTS

READ THIS SECTION FIRST ........................................................................................................ 8

Introduction ............................................................................................................... 8

Impact on installation prerequisites ........................................................................... 8

Modifications on installation prerequisites ................................................................. 8

Modifications on installation procedures .................................................................... 8

Impact on existing ARCAD configuration .................................................................... 8

Client and server product compatibility level ............................................................. 8

Server Requirements ......................................................................................... 8

ARCAD plug-ins version and Client Applications ..................................................... 8

ARCAD version level on remote sites .................................................................... 9

Version installation ................................................................................................ 9

ARCAD migration procedures (Recovery) .................................................................. 9

Modifications in standard macro-commands .............................................................. 9

Other impacts ............................................................................................................. 9

MAJOR ENHANCEMENTS IN THIS VERSION ................................................................................... 10

ARCAD-Open Repository / Process & List Manager .................................................. 10

AADJLSTORD: Dynamic ordering of a list of components ........................................... 10

Manage INDEX before LF in the lists. ................................................................... 10

Macro-command Execution .................................................................................... 10

New Macro-command global variables to retrieve system time and timestamp. ........ 10

New *APP macro variable AAPPMSGD for parameter *MSGD management as components. .................................................................................................... 10

ACPLOBJ: Compilation ........................................................................................... 10

New parameter in ACPLOBJ in order to deactivate the automatic recompilation. ....... 10

AADDAPPLNK/ARMVAPPLNK: Add/Remove link between two applications ..................... 10

New commands to Add or Remove application links. ............................................. 10

All ARCAD modules ............................................................................................... 10

Qualify CRTLIB with QSYS/CRTLIB in order to avoid it calling a specific command which is in-line. ................................................................................................ 10

List Management .................................................................................................. 10

Execution of list process with multi-jobs in parallel. .............................................. 10

ACRTVERLST: Check version and create object lists .................................................. 11

Application links that are held are now respected in the version lists. ...................... 11

ACPLOBJ/ATFROBJ: Compilation/Transfer objects ..................................................... 11

PF to TABLE Conversion: data not kept on target library, when old PF has MAXMBRS(*NOMAX) ......................................................................................... 11

Macros ................................................................................................................ 11

New macros A4EXPORT and A4DEPLOY. .............................................................. 11

ARPLMODSRC: Scan/Replace source from a model.................................................... 11

New command (ARPLMODSRC) to scan and replace source lines from a model. ........ 11

ARCAD-Open Repository/Knowledge Base ............................................................... 11

AUPDPRCREF: Update procedure repository ............................................................. 11

New command to "clean" the procedure repository. .............................................. 11

ACRTSXRLST: Create a list based on source cross-reference ...................................... 12

Requirement to create list of source cross-references for more than 5 levels of nested

/copy clause. ................................................................................................... 12

AUPDXRF: Cross-reference update .......................................................................... 12

Manage RPGLE Key List values for free syntax in the cross-reference calculation +

Transformer Field and Transformer DB. ............................................................... 12




Created by: R&D

Date: 10/05/2017


Page n°3/32

ARCAD-Audit ............................................................................................................ 12

DECLARE2: Declare an application (phase 2)............................................................ 12

Additional information provided when declaring an application. .............................. 12


Improve the library names search when declaring an application. ........................... 12

ARCAD-Skipper 5250 ................................................................................................ 12

RCVNETB: Distribution - Installation ....................................................................... 12

The %LOC keywords are removed from the distributed source members. ................ 12

Check the signature levels for programs and service programs. .............................. 12

ARCAD_DEMO: Application Management sample ...................................................... 12

New application for demonstration and courses. ................................................... 12

ACHKPGMSGN: Check Service Program Signatures ................................................... 12

Check service program links............................................................................... 12

AEDTAPPATR: Edit application attributes .................................................................. 13

Define more profiles for application manager and DB administrator......................... 13

INTEGR: Version integration .................................................................................. 13

Delta integration of a version. ............................................................................ 13

ARCLNUP: Daily procedure ..................................................................................... 13

Improvements to Macro-command ARCLNUP. ...................................................... 13


Operational library specified for more than one application/environment caused compile errors. ................................................................................................. 13


Retrieve the component deletion date in an open version, in the LSTRMV list. .......... 13

ARTVVERD: Retrieve version information ................................................................. 13

Version information: two new parameters for ARTVVERD command. ....................... 13

ARCAD-Skipper ARCAD-Transformer ....................................................................... 13

SQL source files with more than 80 columns. ....................................................... 13

Macros ................................................................................................................ 14

Manage new component types. .......................................................................... 14

ARCAD-Skipper Plugins or Rich Client ...................................................................... 14

Version Management ............................................................................................. 14

New actions: Archive version, Reopen version and Invalidate version. ..................... 14


Support for macros executed from ARCAD commands using INITMACRO and CHKMACRO parameters. .................................................................................... 14

Execute a multi-environment macro-command for a version. ................................. 14

Component Management ....................................................................................... 14

New Environment selection dialog when retrieving components from a test environment. ................................................................................................... 14

ARCAD-Builder for Git ............................................................................................... 14

ARCAD-Skipper for Jira Add-on ................................................................................ 15

ARCAD-Transformer - RPG ........................................................................................ 15

ACVTRPGFRE: Convert RPGLE to Free form .............................................................. 15

Add new Conversion Warnings and Remediation views. ......................................... 15

Problem for conversion of MOVE/MOVEL with negative value when result field is a numeric field. ................................................................................................... 15

ARCAD-Transformer - FIELD ..................................................................................... 16

ACVTPGMFLD: Propagation and automatic modification of program source................... 16

Management of Free and Fully-Free syntax for Transformer Field tool. .................... 16

ARCAD-Transformer - Casetools (ADELIA) ............................................................... 16

New solution to modernize (SQL)RPGLE applications generated by Adelia®. ............ 16




Created by: R&D

Date: 10/05/2017


Page n°4/32

ARCAD-Transformer - Casetools (SYNON®) ............................................................. 16

New solution to modernize (SQL)RPGLE applications generated by Synon®. ............ 16

ARCAD-Anonymizer .................................................................................................. 17

Anonymization Project ........................................................................................... 17

Script Execution ............................................................................................... 17

JDBC Connection Parameters ............................................................................. 17

Option to retry executions if they fail initially ....................................................... 17

Execution Instances .............................................................................................. 17

Emailing results after execution .......................................................................... 17

Scheduling Execution Instance ........................................................................... 17

Anonymization Engines ......................................................................................... 17

Original Value recovering ................................................................................... 17

Duplicate an engine .......................................................................................... 17

Groovy Script Extension .................................................................................... 17

New transformation algorithm: Structured Data engine. ........................................ 17

User Management ................................................................................................. 17

API ..................................................................................................................... 18

Anonymization Web Service ............................................................................... 18

ARCAD-Verifier ......................................................................................................... 18

Context management ............................................................................................ 18

Data context not related to group. ...................................................................... 18

Deliveries ............................................................................................................ 18

Delivery specified through tags. ......................................................................... 18

Campaign management ......................................................................................... 18

Association of tags with scenarios. ...................................................................... 18

Create a campaign manually. ............................................................................. 18

Create a campaign without delivery. ................................................................... 18

Campaign without function. ............................................................................... 18

Scenario execution ............................................................................................... 18

View for running jobs on IBMi............................................................................. 18

File-system comparison ......................................................................................... 18

Matching-pair keys for comparison of File Systems. .............................................. 18

Campaign/Scenario Execution ................................................................................ 18

Next step/action in a Client-Server execution triggered by a timer or an event. ........ 18

ARCAD-Verifier and DOT-Verifier ............................................................................ 19

Sequence of scenario executions in a campaign. ................................................... 19

Campaign execution deletion. ............................................................................ 19

ARCAD-Verifier ..................................................................................................... 19

New DB2 server parameters in RCP. ................................................................... 19

RCP restart .......................................................................................................... 19

RCP restart ...................................................................................................... 19

User information ................................................................................................... 19

Display user login ............................................................................................. 19

"About ARCAD-Verifier" ......................................................................................... 19

RCP version number .......................................................................................... 19

AVRFCHKCPG: Check campaigns of a delivery .......................................................... 19

Check the status of executed campaigns. ............................................................ 19

MOST IMPORTANT CORRECTIONS IN THIS VERSION ....................................................................... 20

ARCAD-Open Repository / Process & List Manager .................................................. 20

Execution of a macro ............................................................................................ 20

Error in ACHGVAR evaluation when '*cat' in lowercase .......................................... 20

ATFROBJ: Transfer objects ..................................................................................... 20

IFS object distribution: error due to authority of save-file. ..................................... 20




Created by: R&D

Date: 10/05/2017


Page n°5/32

Transferred component retains the authorization list and group profile when these are

not on the replaced component. ......................................................................... 20

AWRKSRCTYP: Work with source types.................................................................... 20

SQL C and C++: SQLC and SQLCPP standard IBM types not defined and not managed correctly. ......................................................................................................... 20

AEDTAPSLNK: Work with application/site links ......................................................... 20

Problems when defining more than one screen (subfile) page for the functional modules of a site. ............................................................................................. 20

ACPYIFSOBJ: Copy an IFS Object ........................................................................... 21

Transfer failed if the target IFS path is a shared Linux or a shared windows path. ..... 21

AEXTLST: Extract one list from another ................................................................... 21

Object description text for an existing list not replaced for extract-list command. ..... 21

AADJLSTORD: Dynamic ordering of a list of components ........................................... 21

Determination of a List type did not ignore held records. ....................................... 21

ATFRTOTST: Transfer component to testing environment .......................................... 21

Transfer to test on a remote system fails if the ASP is different. ............................. 21


Wrong owner for certain check-out components. .................................................. 21

Problem with old S/38 components when Event File (*EVENTF) is specified. ............ 21

Source member directive of MAXMBRS(*NOMAX) ignored. ..................................... 21

Compile failed when an SQLRPGLE *SRVPGM used COMPILEOPT(*DUPPROC). ......... 21

Compilation in a version: authorities not retrieved from the reference object. .......... 22

SQL source file length problem. .......................................................................... 22

No authority to delete temporary objects on transfer. ........................................... 22

ACHKSQLSRC: Verify SQL source syntax ................................................................. 22

ARCAD SQL syntax check problems for SQLUDT, SQLPRC and SQLUDF.................... 22

ACRTFLRLST: Create a field cross-reference list ........................................................ 22

Problem with paragraph sign ("§") in field names on field cross-reference. .............. 22

All modules .......................................................................................................... 22

Various English spelling errors. ........................................................................... 22


SQL Syntax check fails for a table with SELECT INTO. ........................................... 22

ATFRSQLOBJ: Transfer an SQL object ..................................................................... 22

SQLSEQ loses current value on transfer. .............................................................. 22

ATFRSRC: Transfer source members ....................................................................... 23

RMVLOCAT not working correctly when transferring source. ................................... 23

ACHKOBJOUT: Check-out object/member ................................................................ 23

Error checking-out files from another version for *USE. ......................................... 23

AGENSQLSRC: Generate SQL source for an SQL Object ............................................. 23

Blank inserted between comparison characters. .................................................... 23

ARCAD-Open Repository / Knowledge Base ............................................................. 23


Procedure and field Cross-reference not correct for an SQLRPGLE in FullyFree. ......... 23

Cross-reference update failed if source member was missing. ................................ 23

Cross-references not updated for SQL CREATE TABLE. .......................................... 23

Error in cross-reference calculation for source SQLRPGLE with *SRVPGM object type.23

Object cross-reference not correct for %EXEC with file name in lowercase. .............. 23

Cross-reference update failed for %ATTR with OPTION(*EVENTF) in a SQLRPGLE

source. ............................................................................................................ 24

Cross-references during DECLARE3 failed if default value DBGVIEW(*ALL) used for CRTBNDRPG..................................................................................................... 24

Field cross-reference for RPGLE not correct for LIKE or LIKEDS in a procedure. ........ 24

ADSPFLDDCT: Display DB field repository ................................................................ 24

Option F4 (Prompt) not working for Display and Field repositories. ......................... 24

AUPDOBJVER: Stamp a component ......................................................................... 24




Created by: R&D

Date: 10/05/2017


Page n°6/32

SQL Variable component update error. ................................................................ 24

ARCAD-Skipper 5250 ................................................................................................ 24

ARMVOBJARC: Delete component modifications ........................................................ 24

Check macro executed too late when removing a component. ................................ 24

ASCNRPLSRC: Scan/Replace a character-string in source members ............................ 24

Error in scan/replace source function when source sequence numbers are absent. .... 24

TFRPROD: Transfer to production ........................................................................... 24

Merge of macro-commands TFRPROD and TFRPRODR. .......................................... 24


Removal of MSGID id when not required. ............................................................. 25

AGENSQLSRC: Generate SQL source for an SQL Object ............................................. 25

Issues managing SQL components ...................................................................... 25

AADDSRCARC: Add a source member ..................................................................... 25

Duplicate component names not prevented when in a higher version. ..................... 25

AUPDOBJCTG: Source member header update ......................................................... 25

Source member line sequence number of 999999 causes error. ............................. 25


Version lists: Localization in recompile list wrong. ................................................. 25

LSTMRG recreated when deleted. ....................................................................... 25

ACRTREFLST: Create repository list......................................................................... 25

Incorrect object library for a list of components from one version to another, when homonyms exist for a component name. ............................................................. 25

ADSPVEROBJ: Display version objects ..................................................................... 26

Wrong environment causes program error. .......................................................... 26

Macros ................................................................................................................ 26

Integration limited to test environment. .............................................................. 26

ADSPMACLOG: Display Macro Log ........................................................................... 26

Possibility to remove an execution instance of a reference macro. .......................... 26

ADSPSRC: Display a component ............................................................................. 26

ADSPSRC: Message not clear when source is missing. ........................................... 26

ARCAD-Skipper Plugins or Rich Client ...................................................................... 26


Object allocation failures not handled by RDi. ....................................................... 26

Macro execution hangs if a macro submits another macro in batch mode. ................ 26

Component Management ....................................................................................... 26

Problem duplicating and renaming IFS components............................................... 26

Error when synchronizing a new Java component that has been renamed before its

first synchronization. ......................................................................................... 26

Repository/Version view is empty or initialized to the wrong version. ...................... 27

Component's source/creation library left blank at creation. .................................... 27

Compilation errors not opened automatically after compilation fails......................... 27

Environment declaration ........................................................................................ 27

Menu option "Declare an environment" does not show........................................... 27

Field renaming propagation .................................................................................... 27

Field renaming propagation preparation uses the wrong environment...................... 27

ARCAD-Transformer - RPG ........................................................................................ 27

ACVTRPGFRE: Convert RPGLE to Free form .............................................................. 27

Conditional indicator not removed for a GOTO left in place of a CABxx. ................... 27

Conversion error with the use of Extended factor 2 in an instruction using a control-level indicator. ................................................................................................. 27

Problem in conversion with usage of ATag = '*LEAVE'. .......................................... 28

New parameter for empty comment lines not visible in the RDi PlugIn..................... 28

Incorrect conversion to Fully-Free, for lines already in Free syntax, with comments in column 1-5 and also literals that continue on the next line. .................................... 28




Created by: R&D

Date: 10/05/2017


Page n°7/32

Instruction DSPLY not converted by ACVTRPGFRE command. ................................. 28

Lost parameters for conversion of a CALL PGM PLIST (parameter list). .................... 28

Incorrect conversion of "EXEC SQL". ................................................................... 28

Problem with program conversion: The call to GTAG_YANAL ended in error (C G D F).28

ARCAD Transformer: RPG error in AARF256M4 due to long numeric initial value. ...... 29

Instruction ADDDUR or SUBDUR not converted. ................................................... 29

Use of "Endif" to test a control level indicator in the middle of an instruction. ........... 29

Incorrect conversion for CABxx or CASxx when test factors and Result indicator are the same. ........................................................................................................ 29

Instruction SHTDN not converted. ....................................................................... 29

ACVTRPGFRE Convert an RPGLE to Free Syntax ........................................................ 29

At the end of the source, adding of a test on "ATag" with no "EndIf" ....................... 29

ARCAD Transformer - DB .......................................................................................... 30

Conversion project management ............................................................................ 30

Updating a conversion project doesn't close in the wizard. ..................................... 30

ARCAD-Transformer - Field ....................................................................................... 30

ACVTPGMFLD: Propagation and automatic modification of program source................... 30

Incorrect propagation with "Return ProcC(parm1 : parm2)". .................................. 30

ARCAD-Verifier ......................................................................................................... 30

ARCAD-Verifier and DOT-Verifier ............................................................................ 30

Managing Mass Exclusions. ................................................................................ 30

Command/Session Interception .............................................................................. 30

Some command interceptions failed during replay. ............................................... 30

AVRFINICDI: Initialize a context ............................................................................. 30

Exclusion of files having special fields of type BLOB, CLOB and DBCLOB. ................. 30

AVRFMNGSD1: Cursor position SBCS/DBCS ............................................................. 30

Anomaly when replaying a scenario with the DBCS emulator which was captured with

SBCS emulator. ................................................................................................ 30

5250 Emulator ..................................................................................................... 30

5250 Emulator may unexpectedly close connection ............................................... 30

Campaign management ......................................................................................... 31

Manually add a scenario to a campaign. .............................................................. 31

Client Engine Screen Comparison ........................................................................... 31

Synchronizing scroll bar for screen comparison editors. ......................................... 31

ARCAD-Observer / DTC ............................................................................................ 31

ASAVDTCGRP: Save a DTC Group ........................................................................... 31

ASAVDTCGRP doesn't save the DTC Types when the DTC group is not valid for all

libraries. .......................................................................................................... 31

ARCAD-Observer / Documenter ................................................................................ 31

Documenter generation and export ......................................................................... 31

Documentation preview fails with File.IOException. ............................................... 31

APPENDIX ........................................................................................................................... 32

ARCAD cumulative standard installation instructions ............................................... 32




Created by: R&D

Date: 10/05/2017


Page n°8/32

READ THIS SECTION FIRST

INTRODUCTION

This document provides you with a list of the corrections included in this release together with the

information you need to use it, the instructions to install it in cumulative mode and the compatibility between the different elements of the solution.

IMPACT ON INSTALLATION PREREQUISITES

Modifications on installation prerequisites

Since version 09.01.00, the ARCAD Plug-ins can only be used with Rational Developer for Power version 8.5 or Rational Developer for i version 9.x

Modifications on installation procedures

If your current installed version is lower than 10.08.00, please execute the following procedure before installing:

• Open an interactive session • Execute the following command:

ARSTDTCGRP DTCGRP(ARCAD_MSG) REPLACE(*NO)

• Log off from the session

Please, you also should read the release notes for each of the versions provided, from your current

ARCAD version to version 10.08.02 and look for changes to the installation procedures.

IMPACT ON EXISTING ARCAD CONFIGURATION

Client and server product compatibility level

Server Requirements

The minimum OS/400 version on the server changed to V7R1.

Required PTF:

With V7R1 (For ARCAD-Transformer RPG)

� SF99701 : DB2 PTF group for free-form RPG with embedded SQL. � 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.

Note that the minimum supported JAVA version is JAVA 1.7

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.

The minimum Rational Developer for I version changed to 9.5.




Created by: R&D

Date: 10/05/2017


Page n°9/32

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.08.02 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




Created by: R&D

Date: 10/05/2017


Page n°10/32

MAJOR ENHANCEMENTS IN THIS VERSION

ARCAD-OPEN REPOSITORY / PROCESS & LIST MANAGER

AADJLSTORD: Dynamic ordering of a list of components

Manage INDEX before LF in the lists.

For the OS Database management, it is more efficient if the INDEX components are created before the LF components so that LFs can reuse/share the INDEX access paths. So now the default sequence number for an INDEX is 5 instead of 6.

The AADJLSTORD command has been changed to take this new priority into account.

Macro-command Execution

New Macro-command global variables to retrieve system time and timestamp.

In order to add specific tests in a macro that depend on the current "time", two new macro global variables have been added: ATIME = System time (hh.mm.ss)

ATIMESTAMP = System date/time (yyyy-mm-dd-hh.mm.ss.cccccc)

New *APP macro variable AAPPMSGD for parameter *MSGD management as components.

In order to test whether or not the application manages message descriptions as components, a new automatic macro variable (AAPPMSGD) can be used to retrieve the value ('Y'/'N') for all types of macro that have an application code.

ACPLOBJ: Compilation

New parameter in ACPLOBJ in order to deactivate the automatic recompilation.

A new parameter CPLMOD1DEP in the ACPLOBJ command can now be used to deactivate the

automatic recompilation of *PGM or *SRVPGM when we compile a *MODULE in a version.

AADDAPPLNK/ARMVAPPLNK: Add/Remove link between two applications

New commands to Add or Remove application links.

New commands similar to AADDVERLNK/ARMVVERLNK have been created for the application level: AADDAPPLNK: Add a link between two applications, the link is modified if it already exists. ARMVAPPLNT: Remove the link between two applications.

All ARCAD modules

Qualify CRTLIB with QSYS/CRTLIB in order to avoid it calling a specific command which is in-line.

In all ARCAD processes, where a CRTLIB is used, it now qualifies the command with QSYS.

This is because in some installations, this command exists in libraries other than QSYS.

List Management

Execution of list process with multi-jobs in parallel.

For some current sequential processes in ARCAD, the duration may be excessive because the process is based on a list of components which are done one after the other. In a batch process, there may only be 15% of the OC used by such a job stream.

An enhancement has been made for some of these processes: it is now possible to execute the process using multiple jobs that run in parallel.




Created by: R&D

Date: 10/05/2017


Page n°11/32

These jobs are controlled by a primary/main job: this may reduce the duration of each process to a

third of the time or better, depending on the system. A new mode of execution MODE(*MULTIJOB) is possible now for these 4 batch commands : - ACPLOBJ Compile a list of objects - AUPDXRF Calculate Cross-references for a list of objects

- ATFROBJ Transfer a list of objects - AEXCLST Execute a command for a list of objects Please read the help of these commands for more information.

ACRTVERLST: Check version and create object lists

Application links that are held are now respected in the version lists.

Version lists LSTLNKAPP and LSTLNKAPP2, created by the ACRTVERLST will now not contain linked

applications that are held (status "H") in the linked-applications screen (AEDTAPPLNK).

ACPLOBJ/ATFROBJ: Compilation/Transfer objects

PF to TABLE Conversion: data not kept on target library, when old PF has MAXMBRS(*NOMAX)

When we convert a PF to a TABLE, the following problem could happen: - The old PF has an attribute MAXMBRS(2, 3 or *NOMAX) - The new TABLE has, by default, only 1 member (limit for TABLE)

But if the old PF has only one member, it now keeps that data, because MAXMBRS(*NOMAX) was not necessary on the old PF.

Macros

New macros A4EXPORT and A4DEPLOY.

Macros for DROPS: Macro A4EXPORT (ARCAD for Drops Export) prepares a save file with the material need to deploy

the version. Macro A4DEPLOY (ARCAD for Drops Deploy) is used to install the version using Drops on the target system.

ARPLMODSRC: Scan/Replace source from a model

New command (ARPLMODSRC) to scan and replace source lines from a model.

This new command has been made available in order to automate the replacement of source lines

according to a "model" which lists the required modifications. The command is used to do and re-do the same modifications in various sources. All the required modifications are entered by the user in a source member which contains one or more "models"; each model contains the lines (or Free RPGLE instructions) to search in the old

source and the corresponding new lines (or Free RPGLE instructions) to replace them.

ARCAD-OPEN REPOSITORY/KNOWLEDGE BASE

AUPDPRCREF: Update procedure repository

New command to "clean" the procedure repository.

The procedure repository was updated only by the AUPDXRF command, which adds procedures. However, when procedures were moved or removed, they were never deleted from the procedure repository.

To compensate for this, the new command AUPDPRCREF can be used to "clean" the procedure repository by removing all procedures which are not "active" for an application.




Created by: R&D

Date: 10/05/2017


Page n°12/32

ACRTSXRLST: Create a list based on source cross-reference

Requirement to create list of source cross-references for more than 5 levels of nested /copy clause.

Now, when we use ACRTSXRLST with RTVSUBLVL(*YES), it allows a search of up to 20 levels of nested COPY statements.

Previously, only 5 levels were processed.

AUPDXRF: Cross-reference update

Manage RPGLE Key List values for free syntax in the cross-reference calculation + Transformer Field and Transformer DB.

When a Free syntax RPGLE doesn't use a KLIST but a list of values for each key element when a file is read with CHAIN, SETLL, READE, etc., the cross-reference calculation for RPGLE now loads fictive

fields named *KLIST00nn for each key ("list of values") and associates the fields as "composite fields". This is also taken into account for:

- Transformer Field, for propagation based on access by key PRPMODE(*ENTITY) - Transformer Field PRPMODE(*DBR), used for AUPDFLDDBR to search for DBR relations in the RPGLE, based on the access by key.

ARCAD-AUDIT

DECLARE2: Declare an application (phase 2)

Additional information provided when declaring an application.

- Additional information for objects without source; - Sources without compilation type are removed from the list of sources without object.


Improve the library names search when declaring an application.

- Scan CL keywords like TOLIB( and FROMLIB( like in CRTDUPOBJ

- Scan other commands CHGCURLIB, CHGSYSLIBL, RMVLIBLE - Allow replacement of qualified name by blanks in a reference library

ARCAD-SKIPPER 5250

RCVNETB: Distribution - Installation

The %LOC keywords are removed from the distributed source members.

This macro, which receives a version, now removes the %LOC keyword in the distributed source members.

Check the signature levels for programs and service programs.

If the control level check is requested for programs, a check of the ILE signatures is also done using new command ACHKPGMSGN.

ARCAD_DEMO: Application Management sample

New application for demonstration and courses.

The previous sample application (SAM) has now been replaced by a library ARCAD_DEMO containing macros to restore and customize applications for demonstration and courses.

ACHKPGMSGN: Check Service Program Signatures

Check service program links.

New command ACHKPGMSGN can now be used to check the consistency of the signatures between a *PGM or *SRVPGM and one or all of the linked service programs.




Created by: R&D

Date: 10/05/2017


Page n°13/32

AEDTAPPATR: Edit application attributes

Define more profiles for application manager and DB administrator.

It is now possible to define more profiles for application manager and DB administrator roles using the AEDTAPPATR command.

Each of those roles can be specified for up to 5 different profiles.

INTEGR: Version integration

Delta integration of a version.

During an integration you can now choose *FULL mode to integrate the whole version or *DELTA mode which will select the components modified since the last integration. The first integration in an environment is *FULL even if *DELTA mode is requested.

It is recommended that in the version control, you change the "Check-recompile" parameter to "*ABNFMT" - ACRTVERLST CHKRCPL(*ABNFMT).

ARCLNUP: Daily procedure

Improvements to Macro-command ARCLNUP.

- Add cleanup of *DTAARA in ARRPLSRC - Remove cleanup of *DTAQ in ARRPLOBJ


Operational library specified for more than one application/environment caused compile errors.

An operational library present in an environment's list can be present in another application or environment, if (and only if) this application does not have the CHKLIB parameter set to *ALL (this parameter). In this special case, the compilation failed.

The problem has been corrected.


Retrieve the component deletion date in an open version, in the LSTRMV list.

In the lists for the deleted components created by ACRTVERLST (lists LSTRMV and LSTRMVOBJ) the date and time were not retrieved. This has been corrected - the date and time values are now set when the deletion is done.

ARTVVERD: Retrieve version information

Version information: two new parameters for ARTVVERD command.

The following parameters have been added to ARTVVERD command: - "In-" parameter "INTENV" with special value *ALL by default, or an environment code. - "Out-" parameter "INTTIME" It is possible now to return the date and time of the last integration for a version and also to select a

specific environment, specified in INTENV.

ARCAD-Skipper ARCAD-Transformer

SQL source files with more than 80 columns.

A palliative was previously set up to take into account SQL source files with over 80 columns. The correction is now integrated into ARCAD processing.




Created by: R&D

Date: 10/05/2017


Page n°14/32

Macros

Manage new component types.

The following macros have been adapted to manage SQL triggers, system triggers and SQL sequences:

GENENV: Generate an environment UPDENV: Upgrade an environment DB

ARCAD-SKIPPER PLUGINS OR RICH CLIENT

Version Management

New actions: Archive version, Reopen version and Invalidate version.

Archive version, Reopen version and Invalidate version actions have been added to ARCAD's GUI. Previously, they could only be run from a 5250 emulator. They are now accessible from the version contextual menu.


Support for macros executed from ARCAD commands using INITMACRO and CHKMACRO parameters.

Some ARCAD commands support the INITMACRO and CHKMACRO parameters to run specific initialization and checking processes using macro commands. Support has been added in order to be able to follow the execution of these macro commands from

ARCAD's GUI.

Execute a multi-environment macro-command for a version.

A new action has been added in the version actions menu, enabling the execution of a multi-environment macro-command on the selected version.

Component Management

New Environment selection dialog when retrieving components from a test environment.

Using the "Retrieve from Test environment" action from the Version Components view will now display a dialog enabling the user to select the test environment from which to retrieve the

components.

ARCAD-BUILDER FOR GIT

ARCAD-Builder is a solution that allows to retrieve IBMi sources from external SCM, upload them on the IBM I, reference them into an ARCAD Repository/Version and execute the ARCAD build macro-command.

The build process definition is defined using a Build Model that can be applied on different ARCAD version. The retrieval of the IBM I Source Members from external SCM is available for Git SCM (Standalone Git, GitHub, Git in Microsoft Team Foundation Server or Visual Studio Team Services). ARCAD-

Builder provides all the necessary mechanisms to detect the delta modification between two tags to only process what have been really modified. The result of the Build Process execution is available into a Build Result that contains: • The IBM I Source Members Import Log

• The IBM I transfer log • The Repository reference execution Log • The Build macro-command execution log

• The execution spooled files The graphical interface is provided as a Web application.




Created by: R&D

Date: 10/05/2017


Page n°15/32

The execution of a Build Process can be triggered using a dedicated JENKINS plug-in in order to

include this process into a global CI process. All the element of the related Build Result are also available as an extension of the Jenkins Build Result Interface.

ARCAD-SKIPPER FOR JIRA ADD-ON

The main goal of the ARCAD-Skipper for Jira add-on is to synchronize JIRA issues and ARCAD Documents (Incident Reports, Change Requests and Maintenance Reports). The JIRA system is the master system and ARCAD the slave. This means that all issues have to be

first created in the JIRA server before they can be created in ARCAD. There are two synchronization operations: • The creation of documents in ARCAD from a JIRA issue (Direction = JIRA > ARCAD)

• The execution of issue transitions according to the ARCAD Document status (Direction ARCAD > JIRA) The main advantages of this solution are:

• The management of the entire synchronization process uses only the JIRA add-on (no need to install other products) and the command line processor • No need to create particular JIRA issue types or custom fields • The administrator can choose when to create ARCAD Documents

• This choice can be different for each issue Type/Project The ARCAD-Skipper add-on is provided with three major elements:

• One Workflow Post Function • One Scheduled Job • A command line processor

The Workflow Post Function allows the user to automatically create an ARCAD document from a JIRA issue at a particular point in the related JIRA issue’s lifecycle. The Scheduled Job regularly retrieves information from the ARCAD system to ultimately update the

JIRA issue’s workflow. The command line processor is an external tool that allows the JIRA add-on communicate with the ARCAD Server.

ARCAD-TRANSFORMER - RPG

ACVTRPGFRE: Convert RPGLE to Free form

Add new Conversion Warnings and Remediation views.

RDi plugin and native: New Conversion Warnings and Conversion Warning Remediation views allow user to override default

conversions on global/member/line basis to deal with possible numeric truncation and/or indicator differences for CHECK, SCAN, LOOKUP in converted source.

Problem for conversion of MOVE/MOVEL with negative value when result field is a numeric field.

For the conversion of MOVE or MOVEL instructions for a numeric field, and when the lengths of Factor 2 and Result field are different, the conversion which uses %EditC(field:'X'), was not OK when the field contains a negative value - an error occurred at the execution.

For all of these cases, the conversion has been changed: a test of the sign of the field is now added first, and then it takes into account the 2 possibilities (positive or negative). Example: Instruction to convert MOVE $Hour P(5,0) to $DecHour P(2,0) Conversion done If $Hour >= 0; $DecHour = %Dec(%Subst(%EditC($Hour:'X'): 4:2):2:0);




Created by: R&D

Date: 10/05/2017


Page n°16/32

Else;

$DecHour = - %Dec(%Subst(%EditC(- $Hour:'X'): 4:2):2:0); EndIf;

ARCAD-TRANSFORMER - FIELD

ACVTPGMFLD: Propagation and automatic modification of program source

Management of Free and Fully-Free syntax for Transformer Field tool.

The 2 new possibilities for RPGLE syntaxes that follow are now taken into account in all the Transformer Field processes:

- Free syntax in column 8-80, for all valid specifications (even declaratives) - Fully-Free syntax, from column 1 to a maximum of 500 characters per line Attention: Some corrections have been done in the cross-reference calculation for RPGLE with Free syntax: all the cross-references must be recalculated before their usage for Transformer Field.

ARCAD-TRANSFORMER - CASETOOLS (ADELIA)

New solution to modernize (SQL)RPGLE applications generated by Adelia®.

A new solution has been provided by ARCAD - as a service - in order to manage the modernization

of Adelia® applications. It allows the reconstruction of all the (SQL)RPGLE generated by Adelia® - after this, they become "understandable" and "maintainable" directly and the Adeliav Case Tools can be abandoned. This transformation is done with an effective ARCAD Tool and allows you to:

- Convert the RPGLE (or RPG) to Free syntax - Externalize all the Adelia® functions as provided ILE procedures - Externalize all the "Management rules" (RGG) or "Adelia® Macros" as applicative ILE procedures

- Rename the Database fields using a long name, derived from the "Adelia® field name" - Rename all the RPGLE fields and subroutines with more meaningful names - and many other features...

ARCAD-TRANSFORMER - CASETOOLS (SYNON®)

New solution to modernize (SQL)RPGLE applications generated by Synon®.

A new solution has been provided by ARCAD - as a service - in order to manage the modernization of Synon® applications; It allows the reconstruction of all the (SQL)RPGLE generated by Synon® - after this, they become

"understandable" and "maintainable" directly and the Synon® Case Tools can be abandoned. This transformation is done with a powerful ARCAD Tool and allows you to: - Convert the RPGLE (or RPG) to Free syntax - Externalize all the Synon® Built-in functions as provided ILE procedures

- Externalize all the Synon® internal functions as applicative ILE procedures - Rename the Database fields using a long name, derived from the "Synon® Field Name" - Rename all the RPGLE fields and subroutines with more meaningful names

- Simplify many parts of the codes (as complex tests, computations, ...) - and many other features...




Created by: R&D

Date: 10/05/2017


Page n°17/32

ARCAD-ANONYMIZER

Anonymization Project

Script Execution

Add a script (batch, shell, ...) to run before or after the anonymization of the file(s). Adding scripts to run can enable you to work with the data to anonymize before or after the transformation is complete.

JDBC Connection Parameters

It’s now possible to customize JDBC parameters Connection (Fetch size, Fetch size direction,

Resultset Type)

Option to retry executions if they fail initially

Define the number of times that the engine should try to transform a field if it encounters an error during the initial anonymization

Execution Instances

Emailing results after execution

Automatically send an email that contains the details of any execution instance after it has been launched, you can also send one manually.

Scheduling Execution Instance

Execution Instance enable you to transform data according to the properties defined in

anonymization projects. Instances can be created from the Execution Instances search view manually or by a schedule defined to create and execute them (regularly) at a later date.

Anonymization Engines

Original Value recovering

If the Save original value (cache required) option is active for an engine, DOT-Anonymizer can recover the original value of your transformed data. The original values from any execution of the

engine (via the test function and an execution instance) are stored in the engine’s cache.

Duplicate an engine

It’s now possible to duplicate an engine

Groovy Script Extension

It’s now possible: - To call an engine transformation in groovy with the following syntax:

data.transformValue("ValueToAnonymize","engineID")

- To reference other fields using properties in Related Fields.

New transformation algorithm: Structured Data engine.

This engine enables you to combine any number of pre-existing rules in the same process. If you have multiple types of content to anonymize in the same project, you can use this engine to define

one algorithm to use for your project that combines all of the rules specific to it.

User Management

A new module that allows to manage User, profiles and rights has been added.




Created by: R&D

Date: 10/05/2017


Page n°18/32

API

Anonymization Web Service

The solution provides a WebService that enables you anonymize websites live.

ARCAD-VERIFIER

Context management

Data context not related to group.

Data contexts are no longer linked to a group.

Deliveries

Delivery specified through tags.

It is now possible to create a delivery without choosing artifacts (cross-reference components) but

by selecting user defined tags. Chosen scenarios on campaign generation are then selected according to their tags.

Campaign management

Association of tags with scenarios.

A new concept of a "tag" has been put in place. The user can define tags then associate them with scenarios. Deliveries can be created for a set of

tags. These tags will determine the scenarios that are executed in the campaigns generated for this delivery.

Create a campaign manually.

It is now possible to manually create a campaign and add scenarios to it.

Create a campaign without delivery.

A campaign can now been created without an associated delivery. Automatic campaign generation from a delivery is still possible.

Campaign without function.

It is now possible to generate campaigns without regard to their original scenario functions. This choice can be made when they are generated or defined in a preference.

Scenario execution

View for running jobs on IBMi

A new view displays running jobs on IBMi related a scenario execution. There is the possibility to stop those jobs.

File-system comparison

Matching-pair keys for comparison of File Systems.

The user can now define the way Verifier will manage matching file pairs in File system comparison.

Campaign/Scenario Execution

Next step/action in a Client-Server execution triggered by a timer or an event.

The user can now define a timer or event (for example the presence of a file in a directory) to trigger the next step in a Client-server scenario.




Created by: R&D

Date: 10/05/2017


Page n°19/32

ARCAD-Verifier and DOT-Verifier

Sequence of scenario executions in a campaign.

Campaign scenarios are now executed in the same order in which they were added to this campaign.

Campaign execution deletion.

A user with an "Archivist" role can delete selected campaign executions. This also removes the associated results and libraries, if necessary.

ARCAD-Verifier

New DB2 server parameters in RCP.

New DB2 server parameters are available in RCP.

Some parameters have also been added that were only available in the IBMi ARCAD-Verifier menu.

RCP restart

RCP restart

It is now possible to restart the RCP Verifier via the file menu

User information

Display user login

The login of the user connected is now displayed in the title bar

"About ARCAD-Verifier"

RCP version number

The RCP version number is now displayed in the "About ARCAD-Verifier"

AVRFCHKCPG: Check campaigns of a delivery

Check the status of executed campaigns.

It is now possible, using the new AVRFCHKCPG command, to check the status of all executed

campaigns associated with a delivery.




Created by: R&D

Date: 10/05/2017


Page n°20/32

MOST IMPORTANT CORRECTIONS IN THIS VERSION

ARCAD-OPEN REPOSITORY / PROCESS & LIST MANAGER

Execution of a macro

Error in ACHGVAR evaluation when '*cat' in lowercase

In a macro, when we use a ACHGVAR ... EXPR(... *cat &WMacVar), at the execution the evaluation of the result macro variable was not correct, because the '*cat' is in lowercase, followed by a macro

variable. The problem is corrected now.

ATFROBJ: Transfer objects

IFS object distribution: error due to authority of save-file.

During the transfer of IFS components using a save-file, an authority problem was sometimes encountered because a save-file is created with *PUBLIC authority *EXCLUDE by default.

This problem has been corrected.

Transferred component retains the authorization list and group profile when these are not on the replaced component.

When transferring components to a more restrictive environment (eg. production), it is possible that the destination component has no authorization list (AUTL) and no Group Profile authorization, where the transferred component has these.

ARCAD did not remove the AUTL when transferring a component, because the RVKOBJAUT does not allow the removal of the AUTL - it must be done using GRTOBJAUT AUTL(*NONE) - and this was not anticipated.

These problems have been corrected.

AWRKSRCTYP: Work with source types

SQL C and C++: SQLC and SQLCPP standard IBM types not defined and not managed correctly.

For 2 IBM standard types: SQLC and SQLCPP, the definitions were not correct or were missing, . These types are now available. Additional note regarding CLE and SQLCLE, CPPLE and SQLCPPLE (C and C++):

these are not official IBM source types, but we may see them as an "object attribute" for *PGM or *MODULE objects. However, in ACRTOBJLST, they are amended/corrected to be the same value as the source type: C, SQLC, CPP, SQLCPP.

AEDTAPSLNK: Work with application/site links

Problems when defining more than one screen (subfile) page for the functional modules of a site.

When adding function-tree codes for the Installed Modules of an Application/Site (AEDTAPSLNK option 5), it was not possible to add more than one page. There was also a problem with the resulting SQL selection string, extracted when using macro variable AENVSFT.

These problems have been corrected.




Created by: R&D

Date: 10/05/2017


Page n°21/32

ACPYIFSOBJ: Copy an IFS Object

Transfer failed if the target IFS path is a shared Linux or a shared windows path.

The IBM CPY command will not accept a parameter value of OWNER(*KEEP) for some file systems, so the ARCAD transfer failed if the target IFS path was a shared Linux or a shared windows path.

This problem has been corrected - the error is now monitored and the CPY OWNER() parameter omitted for these file systems.

AEXTLST: Extract one list from another

Object description text for an existing list not replaced for extract-list command.

A list replaced when extracting one list from another, having a different list description in the TOLISTTEXT() parameter, was not updated with the new description.


AADJLSTORD: Dynamic ordering of a list of components

Determination of a List type did not ignore held records.

When reordering a list to be used for compilations, so that they are performed in the correct sequence, each element on the list must be of type "M" (source member). If there are held elements on the list which are not of type "M", these should be ignored.

However, an error was issued by the command when these elements were in the list. This problem has been corrected.

ATFRTOTST: Transfer component to testing environment

Transfer to test on a remote system fails if the ASP is different.

When components are transferred to test on another system, the ASP for the destination library is normally the same.

However, if it was different, an error occurred when receiving the component on the remote machine. This problem has been corrected.


Wrong owner for certain check-out components.

Some object types (those that ARTVOBJLVL designates type OS and SQL) were owned by the

current user when checked-out and compiled in a version. They should be owned by the same profile as the reference object. This problem has been corrected.

Problem with old S/38 components when Event File (*EVENTF) is specified.

When an Event File (*EVENTF) is requested for general compilations, this should be ignored for S/38 components, eg. type PF38 using QSYS38 library, but it caused an error.


Source member directive of MAXMBRS(*NOMAX) ignored.

A source member directive of %ATTR MAXMBRS(*NOMAX) was ignored, if entered after the component was first compiled in the version. This problem has been corrected.

Compile failed when an SQLRPGLE *SRVPGM used COMPILEOPT(*DUPPROC).

When the compile of an SQLRPGLE service program used CRTSQLRPGI ... COMPILEOPT(*DUPPROC), it failed.





Created by: R&D

Date: 10/05/2017


Page n°22/32

Compilation in a version: authorities not retrieved from the reference object.

The problem that follows is due to an error that appears with version 10.06.13 of ARCAD software. When an object exists in the reference library and this object doesn't exist in the version, when we

check the source out into the version and compile it, it should retrieve the authorities (owner and other authorities) from the reference object, but these authorities were no longer retrieved. This problem has been corrected - the behavior is now as it was before version 10.06.13.

Note: this correction has also now been included in version 10.06.14 (but not documented) and also in the next version.

SQL source file length problem.

When an SQL source file had a length greater than 9999, it caused an error in the compile. This problem has been corrected.

No authority to delete temporary objects on transfer.

When transferring files with dependencies, using the compile method, a profile with minimal authority was not allowed to delete temporary objects. This problem has been corrected.

ACHKSQLSRC: Verify SQL source syntax

ARCAD SQL syntax check problems for SQLUDT, SQLPRC and SQLUDF.

When compiling, SQLUDT (TABLE) containing 'CREATE OR REPLACE FUNCTION" and procedures and functions containing "COMMENT ON PARAMETER xxx" were rejected by the ARCAD SQL syntax checker. These problems have been corrected.

ACRTFLRLST: Create a field cross-reference list

Problem with paragraph sign ("§") in field names on field cross-reference.

There was a error in the field cross-references when field names contained special (language specific) characters. This problem has been corrected.

All modules

Various English spelling errors.

Corrected English spelling and grammatical errors in host macros and message descriptions (and the

related objects compiled over those message descriptions) as well as language strings in RDi .properties files.


SQL Syntax check fails for a table with SELECT INTO.

SQL Syntax check failed for a table with SELECT INTO when the WHERE keyword was not specified. This problem has been corrected.

ATFRSQLOBJ: Transfer an SQL object

SQLSEQ loses current value on transfer.

When transferring an SQLSEQ component, the current value for the replaced (destination) object was lost, due to library list and authority issues. These problems have been corrected.




Created by: R&D

Date: 10/05/2017


Page n°23/32

ATFRSRC: Transfer source members

RMVLOCAT not working correctly when transferring source.

When specifying ATFRSRC RMVLOCAT(*YES) parameter, the %LOC line should be removed from the transferred source, but this did not work as intended.

The problem has been corrected.

ACHKOBJOUT: Check-out object/member

Error checking-out files from another version for *USE.

When trying to check-out a database file from another version for *USE, an error occurred ("invalid object type"). This problem has been corrected.

AGENSQLSRC: Generate SQL source for an SQL Object

Blank inserted between comparison characters.

As part of the transfer process for SQL objects, the source is regenerated (in a temporary file) and the SQL object is re-created. During the manipulation of this source, a space was sometimes inserted between double comparison characters, such as "=", which made the process fail.


ARCAD-OPEN REPOSITORY / KNOWLEDGE BASE


Procedure and field Cross-reference not correct for an SQLRPGLE in FullyFree.

When an SQLRPGLE is written in FullyFree and it uses a /Copy clause, the procedure and field cross-references were not correct. Lines belonging to the COPY clause were not detected and this affected the references in the main source.


Cross-reference update failed if source member was missing.

If, for some reason, the source for a component listed in a version was missing, the cross-reference update a list of objects failed. This problem has been corrected - the missing component is now flagged in the list and the update continues with the next component.

Cross-references not updated for SQL CREATE TABLE.

The CREATE TABLE statement was not recognized by the cross-reference update, when in

component types QRY, QMQRY, SQL, *QMQRY & *QRYDFN, so the relevant cross-references were missing. This problem has been corrected.

Error in cross-reference calculation for source SQLRPGLE with *SRVPGM object type.

When an SQLRPGLE source type is defined to directly create a *SRVPGM, the AUPDXRF process may fail (compilation error, even when the source syntax check is OK).


Object cross-reference not correct for %EXEC with file name in lowercase.

If the ARCAD clause %EXEC is written with lowercase (in file names), the cross-reference may be not complete. This problem has been corrected.




Created by: R&D

Date: 10/05/2017


Page n°24/32

Cross-reference update failed for %ATTR with OPTION(*EVENTF) in a SQLRPGLE source.

If an SQLRPGLE source contains a clause %ATTR OPTION(*EVENTF), the AUPDXRF command fails. This problem has been corrected.

Cross-references during DECLARE3 failed if default value DBGVIEW(*ALL) used for CRTBNDRPG.

An error occurred in the cross-reference update for an RPGLE executed in the DECLARE3 (macro)

process, only when CRTBNDRPG has its default value DBGVIEW(*ALL). This problem has been corrected: For all the RPGLE cross-references (RPGLE or SQLRPGLE for *MODULE or *PGM), it now forces DBGVIEW(*NONE) in the compilation command for cross-reference.

Field cross-reference for RPGLE not correct for LIKE or LIKEDS in a procedure.

In an RPGLE, when local fields of a procedure are declared using LIKE or LIKEDS, based on a single

field or qualified field, the information for the composite fields are not correct (The "Like" link is not visible). This may have an impact on the Transformer Field propagation. The problem has been corrected.

ADSPFLDDCT: Display DB field repository

Option F4 (Prompt) not working for Display and Field repositories.

The same problem occurs with this 2 screens: - ADSPFLDDCT Display field repository - ADSPLITREF Display literal repository When we enter on option for an element then press F4, it exits directly.

This problem has been corrected - it now displays the prompt of the command.

AUPDOBJVER: Stamp a component

SQL Variable component update error.

When specifying CREATE VARIABLE with "... FOR SYSTEM NAME ..." or when using a long ("alias") name, an error occurred when "stamping" the SQLVAR component. This problem has been corrected.

ARCAD-SKIPPER 5250

ARMVOBJARC: Delete component modifications

Check macro executed too late when removing a component.

The macro specified in the CHKMACRO parameter of the ARMVOBJARC command should allow for

termination before any changes are made but this was not the case. The problem has been corrected - if the specified macro cancels processing, no updates are performed by the ARMVOBJARC command.

ASCNRPLSRC: Scan/Replace a character-string in source members

Error in scan/replace source function when source sequence numbers are absent.

The scan and replace command, used in macros such as DECLAR1BB, issued a "record already

exists' error when the source being processed had blank or zero sequence numbers. This problem has been corrected.

TFRPROD: Transfer to production

Merge of macro-commands TFRPROD and TFRPRODR.

To allow the monitoring of both macros (TFRPROD and TFRPRODR) with the RDi plugin, these macros have been merged.




Created by: R&D

Date: 10/05/2017


Page n°25/32


Removal of MSGID id when not required.

Remove messages if the application has parameter "Work with message descriptions as components" = N

AGENSQLSRC: Generate SQL source for an SQL Object

Issues managing SQL components

Some of values were lost by AGENSQLSRC for procedures and functions (*SQLPRC and *SQLUDF types) in the SET OPTION section: DATFMT, DATSEP, TIMFMT, TIMSEP. This problem is fixed.

AADDSRCARC: Add a source member

Duplicate component names not prevented when in a higher version.

When adding a new component to a version, ARCAD checks that there is not an existing component with the same name and type. This check was only done for versions below the current version, so if the existing component was in a higher version, a duplicate additional component could be added in error.


AUPDOBJCTG: Source member header update

Source member line sequence number of 999999 causes error.

If a source member had a sequence number of 999999 it sometimes caused an error when inserting the automatic header lines. This problem has been corrected.


Version lists: Localization in recompile list wrong.

When executing a ATFRSRC using the LSTRCPL list, the localization (*L01, *L02, etc.) was wrong, even with ATFRSRC FRCLOCAT(*NO) specified. This problem has been corrected.

LSTMRG recreated when deleted.

The list of components to be merged with other versions (LSTMRG) is created when the version is opened.

However, if it was deleted, it was not recreated. This problem has been corrected - the "create version lists" process will create the LSTMRG in another version when necessary.

ACRTREFLST: Create repository list

Incorrect object library for a list of components from one version to another, when homonyms exist for a component name.

In an application, if several components exist with the same name but with different source types and/or object types (homonyms), when we use ACRTREFLST to get a "cumulative list" from a version number to a higher version number, the source or object library may be incorrect when a component has more than one modification - it may not be the last modification version for each

component. This problem has been corrected.




Created by: R&D

Date: 10/05/2017


Page n°26/32

ADSPVEROBJ: Display version objects

Wrong environment causes program error.

When a wrong environment was entered when displaying the objects for a version, it caused the command to crash.

This problem has been corrected - the correct validation of environment and version are now done.

Macros

Integration limited to test environment.

INTEGR: Version integration. A wrong value was tested when checking if the integration was requested for a valid environment Id. It was possible to make an integration in the reference environment.


ADSPMACLOG: Display Macro Log

Possibility to remove an execution instance of a reference macro.

Use of ADSPMACLOG for a reference macro and option 4 in front on an execution instance failed with CPF4101. This problem has been corrected - option 4 now deletes the instance correctly.

ADSPSRC: Display a component

ADSPSRC: Message not clear when source is missing.

When there is a problem displaying the requested source, such as a missing source member of a library that has been renamed, the retrieved source is from the latest version. This is confirmed by a message before display, but was not clear. The problem has been corrected - the message is now more explicit and consistent.

ARCAD-SKIPPER PLUGINS OR RICH CLIENT


Object allocation failures not handled by RDi.

When the ALCKOBJ command was run from a macro command executed under RDi and it failed, the

interruption was not handled by RDi and the macro job would stay in MSGW. This problem has been corrected - allocation errors are now handled by RDi if executed from a macro command.

Macro execution hangs if a macro submits another macro in batch mode.

If a macro was executed from the ARCAD Client or the Skipper plugins and if this macro submitted another macro in batch mode, then no other communication could occur between the macro engine

and RDi. This problem has been corrected.

Component Management

Problem duplicating and renaming IFS components.

Duplicating or renaming an IFS component from the Repository or Version Component view wasn't working for IFS components.


Error when synchronizing a new Java component that has been renamed before its first synchronization.

When a new Java component was renamed before being synchronized at least once, an error occurred and the component was then deleted.




Created by: R&D

Date: 10/05/2017


Page n°27/32


Repository/Version view is empty or initialized to the wrong version.

After RDi startup, the Repository or Version components view would not always be restored to their previous state.

Moreover, this caused another issue preventing these views from being correctly refreshed. The problem has been corrected.

Component's source/creation library left blank at creation.

When a new component was created and its topology allowed the selection of a source/creation library, those fields could be left blank, leading to the wrong library being used at creation. This problem has been corrected.

Compilation errors not opened automatically after compilation fails.

After a compilation failure, the compilation error view did not show up even if the option was

enabled in the preferences. This problem has been corrected.

Environment declaration

Menu option "Declare an environment" does not show.

The "Declare an environment" action was hidden from the user when not an Administrator. This problem has been corrected.

Field renaming propagation

Field renaming propagation preparation uses the wrong environment.

If an application held more than one development environment, there was a chance that the Field

Renaming Propagation Preparation action was called with the wrong environment ID. This problem has been corrected.

ARCAD-TRANSFORMER - RPG

ACVTRPGFRE: Convert RPGLE to Free form

Conditional indicator not removed for a GOTO left in place of a CABxx.

If an instruction to convert contains a CABxx operation code, but also has conditional indicators in column 7-11: C KA COR KCREAX cabeq *BLANKS RETURN When the GOTO can't be replaced (because it's outside a subroutine), the conversion was wrong - it

left the indicators in column 7-11: If *InKA or *InKC; If REAX = *BLANKS; COR KC Goto RETURN EndIf; Endif; This problem has been corrected.

Conversion error with the use of Extended factor 2 in an instruction using a control-level indicator.

When a source contains an instruction using a "Control level indicator" in column 7-8, and this instruction has an extended Factor 2 which continues on the next line, like this: CL1 eval ecrlib=%trim(ecrlib)+'/'+devcodecr+ C $mt8; the conversion to free syntax may end abnormally or it may be not correct. This problem has been corrected.




Created by: R&D

Date: 10/05/2017


Page n°28/32

Problem in conversion with usage of ATag = '*LEAVE'.

When the conversion (for GOTO...TAG) needed to use ATag = '*LEAVE' or ATag = '*ITER', the conversion was not correct, because the ATag field was not reset to blanks when it reached the last

loop to leave or iterate. This problem has been corrected.

New parameter for empty comment lines not visible in the RDi PlugIn.

A new parameter - EMPTYCMT - was added to the ACVTRPGFRE command in version 10.06.13. These lines can be deleted (*REMOVE), consolidated to a single blank line (*ONELINE), set to blank comments, with "//" (*KEEP) or blank lines (*BLANK).

However, it was not possible to see and change this new parameter in the RDi plugIn (in "Preferences" and when we run a conversion). This problem has been corrected.

Incorrect conversion to Fully-Free, for lines already in Free syntax, with comments in column 1-5 and also literals that continue on the next line.

In an RPGLE source to convert, if some lines are already in Free syntax (column 8-80) and contain a

literal split over several lines, using a '-' or '+' to continue on the next line, and on these lines, comments also exist in columns 1-5: When we launch the conversion to Fully-Free, and we want to keep the comments that were on

column 1-5 using FLGCVTTYPE(*KEEP), the converted source was not OK for compilation. This is because these comments are moved at the end of each line, but the RPGLE compiler doesn't allow comments after the '-' or '+' in a literal which continues to the next line. This problem has been corrected - for these lines, the comments are removed.

Instruction DSPLY not converted by ACVTRPGFRE command.

When the instruction DSPLY is used with no value in Factor 1, it was not converted to Free syntax.

This problem has been corrected: it is now converted as: DSPLY '' '' FactR;

Lost parameters for conversion of a CALL PGM PLIST (parameter list).

Before the conversion, the Field Cross References are calculated for the RPGLE ; but these could be not completed in the following cases: - Use of compilation directives (IF, /ELSEIF..) on the line just before the 'Ctl-Opt' specification, when

it contains INDENT(' ) or OPTION(*SRCSTMT) - Use of a comment with C-Spec ("C*"), before including a /COPY clause for the "H" or "Ctl-Opt" specification. The consequence in Transformer RPG was that the conversion of a CALL using a PLIST was incorrect

(no parameters were retrieved). This problem has been corrected.

Incorrect conversion of "EXEC SQL".

In a source, When we have a "calculation specification" in free form, just followed by "C/Exec Sql", the conversion may be wrong, like this: /exec sql If *InRE; This problem has been corrected.

Problem with program conversion: The call to GTAG_YANAL ended in error (C G D F).

When the source to convert already contains a Free form calculation specification (with no C/Free before), a problem could occur in the conversion: "The call to GTAG_YANAL ended in error...."





Created by: R&D

Date: 10/05/2017


Page n°29/32

ARCAD Transformer: RPG error in AARF256M4 due to long numeric initial value.

In the source to be converted, when we encounter a D-Spec which contains a default numeric value with more than 9 digits - ex: INZ(1234567980 -, the conversion fails, (error RNX0103 in module

AARF256M4). This problem has been corrected.

Instruction ADDDUR or SUBDUR not converted.

When a date or time literal is used on Factor 1 or 2 of a date/time instruction (ADDDUR, SUBDUR, EXTRCT), the instruction was not converted to Free form. This problem has been corrected.

Use of "Endif" to test a control level indicator in the middle of an instruction.

When the last instruction of a block of instructions which uses a "Control level indicator L1, L2, ..."

uses more than one line in classical syntax, the instruction "CLx Endif" is not added after all the lines for this instruction. Example : Original source: CL2 99 CANNLR exsr NEWPAG Converted source with error: CL2 If *InL2 If *In99 CL2 EndIf and not *InLR; Exsr NEWPAG; Endif; This problem has been corrected.

Incorrect conversion for CABxx or CASxx when test factors and Result indicator are the same.

The conversion was not correct for CABxx or CASxx instructions which also use a result indicator, when the result indicator is also one of the 2 factors which are compared.

Eg: *IN99 CABEQ '0' TAG99 99 The problem has been corrected: in this case, it now uses more lines in order to respect the behavior of the CABxx or CASxx instruction.

Instruction SHTDN not converted.

The SHTDN instruction was not converted.

This problem has been corrected - it now uses %ShtDn.

ACVTRPGFRE Convert an RPGLE to Free Syntax

At the end of the source, adding of a test on "ATag" with no "EndIf"

The following case could occur : at the end of the main part of the source, when a TAG is removed (and managed with just a "Leave", the new source could have a test of "ATag" not useful (and with no "EndIf") :

... EndDo If ATag = *Blanks; // END OF PROGRAM

*INLR = '1'; The problem is corrected now: the test is removed.




Created by: R&D

Date: 10/05/2017


Page n°30/32

ARCAD TRANSFORMER - DB

Conversion project management

Updating a conversion project doesn't close in the wizard.

When a conversion project was updated, clicking on Finish in the wizard did not close it, even though the project was successfully updated. This problem has been corrected.

ARCAD-TRANSFORMER - FIELD

ACVTPGMFLD: Propagation and automatic modification of program source

Incorrect propagation with "Return ProcC(parm1 : parm2)".

When a field "parm1" is propagated and used in a RETURN instruction like this:

Return ProcC(parm1 : parm2) an invalid propagation was done from "parm1" to "ProcC". This problem has been corrected.

ARCAD-VERIFIER

ARCAD-Verifier and DOT-Verifier

Managing Mass Exclusions.

A new view is used to globally manage the exclusion of files, tables or fields for data comparison.

Command/Session Interception

Some command interceptions failed during replay.

Running STRPCO, CLRLIB LIB(QTEMP), CHGLIBL commands during a replay, caused errors. These problems have been corrected.

AVRFINICDI: Initialize a context

Exclusion of files having special fields of type BLOB, CLOB and DBCLOB.

During the generation of a data context, any files having fields defined as BLOB, CLOB or DBCLOB are automatically excluded.

AVRFMNGSD1: Cursor position SBCS/DBCS

Anomaly when replaying a scenario with the DBCS emulator which was captured with SBCS emulator.

5250 emulators:

The coding of the cursor position is different between the ARCAD SBCS and ARCAD DBCS emulators, so it is necessary to convert the actions recorded with the SBCS emulator, in order to replay it with the DBCS emulator. The AVRFMNGSD1 command allows this modification, with a choice of scenarios to be transformed,

rollbacks and checks.

5250 Emulator

5250 Emulator may unexpectedly close connection

During the recording of a scenario the 5250 DBCS emulator may close the connection to the server unexpectedly during a screen change, this is not directly related to DBCS and is constantly occurring at the same place.

This error is now handled and the screen correctly displayed.




Created by: R&D

Date: 10/05/2017


Page n°31/32

Campaign management

Manually add a scenario to a campaign.

A check has been added: all scenarios in a campaign should have the same engine.

Client Engine Screen Comparison

Synchronizing scroll bar for screen comparison editors.

The scroll bars of the two panels containing the screenshots (from the compared and the reference

result are now synchronized. Additionally, the image of the screenshot is now fully displayed.

ARCAD-OBSERVER / DTC

ASAVDTCGRP: Save a DTC Group

ASAVDTCGRP doesn't save the DTC Types when the DTC group is not valid for all libraries.

The ASAVDTCGRP command doesn't save any DTC types, when the types in the DTC group are not valid for all libraries : - Valid for all applications . . .: N

- or Usable on libs. without appli. .: N ASAVDTCGRP uses a ACRTDTCLST with OUTTYPE(*DTCTYP) and this should not check the DTC types against the application library. The problem has been corrected - the application library is now only checked (for each DTC type)

when OUTTYPE(*FILE), not OUTTYPE(*DTCTYP).

ARCAD-OBSERVER / DOCUMENTER

Documenter generation and export

Documentation preview fails with File.IOException.

The documentation preview failed if the user running the product did not have enough authority to write to the Documenter plugin installation directory. This problem has been corrected.




Created by: R&D

Date: 10/05/2017


Page n°32/32

APPENDIX

ARCAD CUMULATIVE STANDARD INSTALLATION INSTRUCTIONS

Use this procedure to apply version 10.08.02 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.