VisualAge Pacbase AIX, HP-UX, Sun Solaris,HP Tru64 Unix 3.5 Y04A (CSD) E

Technote (FAQ)


Question

List of changes of the VisualAge Pacbase AIX, HP-UX, Sun Solaris, HP Tru64 Unix 3.5 Y04A version

Answer


VISUALAGE PACBASE AIX 3.5 Y04A(CSD)

NEW FUNCTIONALITIES

Administration

Batch procedure to manage use rights assignment
(UKD1).
(C:028934)
New batch procedure to manage use rights.
This procedure has two functions:
- Assign use rights to a group of users
- Activate a new access key
User input:
. Identification line with administrator user code
and password.
. K-line to activate an access key
('K' followed by the 14-characters access key identifier)
-- the key must already be defined in the database.
. U-line to modify or assign use rights (optional)
("UusercodeTYP1xTYP2xTYP3x etc.")
TYPn (4 characters) is the type of use right to be assigned
(maximum of 10 seats by line) :
CO1 : Designer
IW1 : Developer for Developer workbench
PA1 : Text User Interface for VA Pac in character-mode.
LE1 : Reader
T1n : Traditional build facility Mono-target n
T2n : Traditional build facility Bi-target n
TM1 : Traditional build facility Multi-target
E1n : eBusiness build facility Mono-target n
E2n : eBusiness build facility Bi-target n
EM1 : eBusiness build facility Multi-target
The x characters corresponds to the permanent assignment
of the right (1 if permanent).

The transactions generated after the use rights
modifications will take into account the possible new
access key.
Therefore the modification of the access key must be entered
before the U-line(s).

Caution: this procedure updates the administration database,
the files must be closed to online use.

Batch System Development

Cobol II ('D') generation language: STOP RUN is
now ganerated instead of STOP 'literal'.
(C:027032)
Cobol II ('D') generation language: STOP RUN is now
ganerated instead of STOP 'literal'.

When a batch program uses one or more VSAM files with a
fixed length, the generated source then contains function
F0A90. Until now, this function contained
STOP 'INPUT-OUTPUT ERROR. CANCEL THE JOB'.
If the generated language is cobol II ('D' in the 'Generated
language' field in the Library Definition), STOP RUN now
replaces STOP 'literal'.

Addition of a field containing the Pacbase version
and the generator version in "Pacbase Constants".
(C:027492)
Creation of a field containing the Pacbase version and the
generator version.
Addition of 3 areas in the PACBASE constants:
05 RELEAS PICTURE X(7). -- version (ex : 3.5 V
05 DATGE PICTURE X(10). -- generator date
05 DATSQ PICTURE X(10). -- skeleton date
!! The CONSTANTS area goes up from X(60) to X(87)

New operator: MOVE CORRESPONDING between two
COBOL fields
(C:027731)
Definition of a new operator:
-----------------------------
MOVE CORRESPONDING between two Cobol group fields
Syntax: MCI OPERANDE1 OPERANDE2
A postprocessor has been developed and is included in
the new procedure BVPGPMC.
Implementation:
---------------
For any area of the Data Division of a program (Batch,
Online).
Result:
-------
A move is generated for each elementary area having the same
code in the 2 operands. The linking criterion corresponds
to the string behind the first '-'.
The occurs is taken into account if it is specified at the
operand level (A or/and 2).
Limits:
-------
Only one target (only one OPERANDE2).
No consistency control.
The picture is not taken into account.
"MOVE ZONE OF ZONEB" Cobol option not taken into account.

Parameterization of the DO operator counter
(C:027732)

Parameterization of the DO operator counter.
It is now possible to choose the variable which will
used as counter for the DO operator.
In the condition area, it is possible to define the name
of the index used in the DO loop. Addition of a parameter
in first position of the DO condition, coded as follows:
I=zoneind where 'zoneind' corresponds to a working area
declared by the user.

Date Data Elements can be broken down into
elementary fields.
(C:027735)
Data Elements with a date format can be broken down into
elementary fields which clearly represent the day, month
and year.
An option, BREAKDATE=YES, can now be entered in the
Generation Options (-GO) of:
- a Library,
- a Dialog,
- a C/S Application,
- a Program.
In a Program, the BREAKDATE=NO option can be entered in the
Generation Options (-GO) to avoid the breakdown of dates in
this particular Program, even if the option is set to
YES at the Library level.
NB: This option must be entered alone on a line and must
begin in column 1.

New option for the generation of DB2 Segments in
the host variables
(C:027736)
A new generation option for DB2 Segments makes it possible
to include, in the hosts variables, all the Data Elements
called in the Segment.
This new option, DESCR=ALL, is to be entered on the
Generation Options (-GO) of Q2-type SQL Database Blocks.
This change is linked to the change 27735.

The format of manipulated dates is no more
required for the operations on dates
(C:028200)
The format of manipulated dates is no more required for
the operations on dates. The format of the data elements
declared as dates is automatically extracted from the
repository.

Key, license

Batch procedure to manage use rights assignment
(UKD1).
(C:028934)
New batch procedure to manage use rights.
This procedure has two functions:
- Assign use rights to a group of users
- Activate a new access key
User input:
. Identification line with administrator user code
and password.
. K-line to activate an access key
('K' followed by the 14-characters access key identifier)
-- the key must already be defined in the database.
. U-line to modify or assign use rights (optional)
("UusercodeTYP1xTYP2xTYP3x etc.")
TYPn (4 characters) is the type of use right to be assigned
(maximum of 10 seats by line) :
CO1 : Designer
IW1 : Developer for Developer workbench
PA1 : Text User Interface for VA Pac in character-mode.
LE1 : Reader
T1n : Traditional build facility Mono-target n
T2n : Traditional build facility Bi-target n
TM1 : Traditional build facility Multi-target
E1n : eBusiness build facility Mono-target n
E2n : eBusiness build facility Bi-target n
EM1 : eBusiness build facility Multi-target
The x characters corresponds to the permanent assignment
of the right (1 if permanent).

The transactions generated after the use rights
modifications will take into account the possible new
access key.
Therefore the modification of the access key must be entered
before the U-line(s).

Caution: this procedure updates the administration database,
the files must be closed to online use.

Client/Server system develop.

Variant capture is controlled
(C:024751)

When variants are updated (batch, dialog, dbd, dialog C/S,
eBusiness), they are controlled and limited to those
indicated in the "IBM Software Annoucement letter".

Addition of a field containing the Pacbase version
and the generator version in "Pacbase Constants".
(C:027492)
Creation of a field containing the Pacbase version and the
generator version.
Addition of 3 areas in the PACBASE constants:
05 RELEAS PICTURE X(7). -- version (ex : 3.5 V
05 DATGE PICTURE X(10). -- generator date
05 DATSQ PICTURE X(10). -- skeleton date
!! The CONSTANTS area goes up from X(60) to X(87)

New operator: MOVE CORRESPONDING between two
COBOL fields
(C:027731)
Definition of a new operator:
-----------------------------
MOVE CORRESPONDING between two Cobol group fields
Syntax: MCI OPERANDE1 OPERANDE2
A postprocessor has been developed and is included in
the new procedure BVPGPMC.
Implementation:
---------------
For any area of the Data Division of a program (Batch,
Online).
Result:
-------
A move is generated for each elementary area having the same
code in the 2 operands. The linking criterion corresponds
to the string behind the first '-'.
The occurs is taken into account if it is specified at the
operand level (A or/and 2).
Limits:
-------
Only one target (only one OPERANDE2).
No consistency control.
The picture is not taken into account.
"MOVE ZONE OF ZONEB" Cobol option not taken into account.

Date Data Elements can be broken down into
elementary fields.
(C:027735)
Data Elements with a date format can be broken down into
elementary fields which clearly represent the day, month
and year.
An option, BREAKDATE=YES, can now be entered in the
Generation Options (-GO) of:
- a Library,
- a Dialog,
- a C/S Application,
- a Program.
In a Program, the BREAKDATE=NO option can be entered in the
Generation Options (-GO) to avoid the breakdown of dates in
this particular Program, even if the option is set to
YES at the Library level.
NB: This option must be entered alone on a line and must
begin in column 1.

New option for the generation of DB2 Segments in
the host variables
(C:027736)
A new generation option for DB2 Segments makes it possible
to include, in the hosts variables, all the Data Elements
called in the Segment.
This new option, DESCR=ALL, is to be entered on the
Generation Options (-GO) of Q2-type SQL Database Blocks.
This change is linked to the change 27735.

IMS target: CBLTDLI calls replaced by CEETDLI
calls for a 'generated language' set to D
(C:028403)
Generation of calls to CEETDLI for IMS

All the calls to CBLTDLI are replaced by calls to CEETDLI
if the 'GENERATED LANGUAGE' of the generation library is
set to 'D'.

Client/Server system dev. 3.x

Parameterization of the DO operator counter
(C:027732)

Parameterization of the DO operator counter.
It is now possible to choose the variable which will
used as counter for the DO operator.
In the condition area, it is possible to define the name
of the index used in the DO loop. Addition of a parameter
in first position of the DO condition, coded as follows:
I=zoneind where 'zoneind' corresponds to a working area
declared by the user.

New condition types for date control: DV and DI
(C:027733)

New condition types to control the dates.
Processing under the condition of validity or invalidity
of a date. To do so, two new condition types have been
added:
DV: execution of the processing if the date specified in
the condition area is valid.
DI: execution of the processing if the date specified in
the condition area is not valid.
First character of condition area must be the date format
(ex : DV D datefield).

Monitor and Folder Manager: modification of the
work file management.
(C:027855)
Monitor and Folder Manager: modification of the work file
management.
There is a write access to the work file if:
- a user buffer is used,
- the request is sent via more than one message,
- the response causes a capacity overflow.
A record can then be created either in the Communication
Monitor or in the Folder.

Warining: this optimization requires the Communication
Monitor and the Folder managers linked to it ('eBusiness'
entity) to be generated again with this optimization.

Make it possible to call n SQL physical access
from description lines.
(C:027959)
Dialogue and Elementary Components: the purpose is to make
it possible to call SQL non-standard physical access, which
are partly described in the description lines of a Segment
representing a SQL table.
If the user has coded a sub-function, in a function F80,
with *C as a condition type and ffnn A1=S1 as a condition,
with A1 corresponding to a non-standard access described
in the Segment, and S1 corresponding to one of the
non-standard access which are taken into account by the
generator, then, the access generation is including the
information described by the user in the Segment.
They are completed by
other useful information such
as: the column name, the host-variable, the external name
of the table... depending on the standard access-type
defined.
For a DECLARE CURSOR (DC), the user is responsible for
positioning the clause WHERE (as for the Program entity).

New operator giving the difference between two
dates: DAD
(C:027960)
New operator giving the difference between two dates.
deux dates
Creation of the new operator DAD 'Date Difference'.
In the operand field, the syntax of the operation is as
follows:
xy ffnn-Date1 ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
The result is stored in an area, NUM-DAYS, automatically
declared in working.

New condition based on the comparison between two
dates: DC
(C:027961)
New condition based on the comparison between two dates.
Creation of the new condition type DC in the condition
field. The syntax is as follows:
xy ffnn-Date1 oper ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
oper corresponds to the comparison type and
can have the following values:
> or < or > = or < = or = or NOT > or NOT < or NOT=
If this condition type is assigned to a subfunction,
the comparison test must be followed by the processing:
NEXT SENTENCE ELSE GO TO Fffss-FN.

'C'-type Screens can call Elementary Components.
(C:027978)

Now a 'C'-type Screen (C/S Screen or TUI Client) can call
a 3.x Elementary Component.

"CURSOR FOR UPDATE" clause taken into account in
the DB2 update orders
(C:028064)
"CURSOR FOR UPDATE" clause taken into account in the DB2
update orders for eBusiness elementary components.
Addition of a new CURSUPDT=YES option that can be defined
either at library level or at C/S Application level.
If this option is chosen, the SELECT SQL orders for update
are replaced by an OPEN CURSOR FOR UPDATE.

Availability of the separator option for data
elements defined with a date or time format
(C:028066)
The separator option for data elements defined with a date
format (E-M-G) or time format (T) is now available.
The separator must be entered on the second character of the
format field (input, internal, output).
Examples: M-,G/,E-,T: ....

New ERS operator for system errors in the
eBusiness module
(C:028081)
Programming of system errors in the eBusiness module.
The new ERS operator is available.
This operator sets a system error and a branch to the
program end is systematically generated (F81RE for the
components and in F97ER for the monitors and Folder
manager).

The format of manipulated dates is no more
required for the operations on dates
(C:028200)
The format of manipulated dates is no more required for
the operations on dates. The format of the data elements
declared as dates is automatically extracted from the
repository.

IMS target: CBLTDLI calls replaced by CEETDLI
calls for a 'generated language' set to D
(C:028403)
Generation of calls to CEETDLI for IMS

All the calls to CBLTDLI are replaced by calls to CEETDLI
if the 'GENERATED LANGUAGE' of the generation library is
set to 'D'.

eBusiness Module

Monitor and Folder Manager: modification of the
work file management.
(C:027855)
Monitor and Folder Manager: modification of the work file
management.
There is a write access to the work file if:
- a user buffer is used,
- the request is sent via more than one message,
- the response causes a capacity overflow.
A record can then be created either in the Communication
Monitor or in the Folder.

Warining: this optimization requires the Communication
Monitor and the Folder managers linked to it ('eBusiness'
entity) to be generated again with this optimization.

In extract methods, the * and + operators are now
replaced with AND and OR.
(C:028988)
In extract methods, you can now use the AND and OR
operators instead of * and +

Generators

New operators: MC (Move Corresponding) and
MF (Move Function)
(C:022585)
Definition of two new operators:
- MC for Move Corresponding
Syntax: MC ident1 ident2
Generated code: MOVE CORR ident1 TO IDENT2
- MF for Move Function
Syntax: MF 'function' (parameter1) parameter2
Generated code: MOVE FUNCTION 'function' (parameter1) TO
parametre2
'function' is one of Cobol intrinsec functions such as
UPPER-CASE.

Cobol II ('D') generation language: STOP RUN is
now ganerated instead of STOP 'literal'.
(C:027032)
Cobol II ('D') generation language: STOP RUN is now
ganerated instead of STOP 'literal'.

When a batch program uses one or more VSAM files with a
fixed length, the generated source then contains function
F0A90. Until now, this function contained
STOP 'INPUT-OUTPUT ERROR. CANCEL THE JOB'.
If the generated language is cobol II ('D' in the 'Generated
language' field in the Library Definition), STOP RUN now
replaces STOP 'literal'.

New operator: MOVE CORRESPONDING between two
COBOL fields
(C:027731)
Definition of a new operator:
-----------------------------
MOVE CORRESPONDING between two Cobol group fields
Syntax: MCI OPERANDE1 OPERANDE2
A postprocessor has been developed and is included in
the new procedure BVPGPMC.
Implementation:
---------------
For any area of the Data Division of a program (Batch,
Online).
Result:
-------
A move is generated for each elementary area having the same
code in the 2 operands. The linking criterion corresponds
to the string behind the first '-'.
The occurs is taken into account if it is specified at the
operand level (A or/and 2).
Limits:
-------
Only one target (only one OPERANDE2).
No consistency control.
The picture is not taken into account.
"MOVE ZONE OF ZONEB" Cobol option not taken into account.

Parameterization of the DO operator counter
(C:027732)

Parameterization of the DO operator counter.
It is now possible to choose the variable which will
used as counter for the DO operator.
In the condition area, it is possible to define the name
of the index used in the DO loop. Addition of a parameter
in first position of the DO condition, coded as follows:
I=zoneind where 'zoneind' corresponds to a working area
declared by the user.

New condition types for date control: DV and DI
(C:027733)

New condition types to control the dates.
Processing under the condition of validity or invalidity
of a date. To do so, two new condition types have been
added:
DV: execution of the processing if the date specified in
the condition area is valid.
DI: execution of the processing if the date specified in
the condition area is not valid.
First character of condition area must be the date format
(ex : DV D datefield).

New operator for operations on dates: DAO
(C:027734)

New operator for operations on dates: DAO.
This operator is used to add or substract a number of days
to the variable declared in date format in the repository.
Syntax :
DAO x snnnn date1
x = date format
s = '+' or '-'
nnnn = number or numeric field
date1 = Input and output date field

Date Data Elements can be broken down into
elementary fields.
(C:027735)
Data Elements with a date format can be broken down into
elementary fields which clearly represent the day, month
and year.
An option, BREAKDATE=YES, can now be entered in the
Generation Options (-GO) of:
- a Library,
- a Dialog,
- a C/S Application,
- a Program.
In a Program, the BREAKDATE=NO option can be entered in the
Generation Options (-GO) to avoid the breakdown of dates in
this particular Program, even if the option is set to
YES at the Library level.
NB: This option must be entered alone on a line and must
begin in column 1.

Make it possible to call n SQL physical access
from description lines.
(C:027959)
Dialogue and Elementary Components: the purpose is to make
it possible to call SQL non-standard physical access, which
are partly described in the description lines of a Segment
representing a SQL table.
If the user has coded a sub-function, in a function F80,
with *C as a condition type and ffnn A1=S1 as a condition,
with A1 corresponding to a non-standard access described
in the Segment, and S1 corresponding to one of the
non-standard access which are taken into account by the
generator, then, the access generation is including the
information described by the user in the Segment.
They are completed by
other useful information such
as: the column name, the host-variable, the external name
of the table... depending on the standard access-type
defined.
For a DECLARE CURSOR (DC), the user is responsible for
positioning the clause WHERE (as for the Program entity).

New operator giving the difference between two
dates: DAD
(C:027960)
New operator giving the difference between two dates.
deux dates
Creation of the new operator DAD 'Date Difference'.
In the operand field, the syntax of the operation is as
follows:
xy ffnn-Date1 ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
The result is stored in an area, NUM-DAYS, automatically
declared in working.

New condition based on the comparison between two
dates: DC
(C:027961)
New condition based on the comparison between two dates.
Creation of the new condition type DC in the condition
field. The syntax is as follows:
xy ffnn-Date1 oper ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
oper corresponds to the comparison type and
can have the following values:
> or < or > = or < = or = or NOT > or NOT < or NOT=
If this condition type is assigned to a subfunction,
the comparison test must be followed by the processing:
NEXT SENTENCE ELSE GO TO Fffss-FN.

"CURSOR FOR UPDATE" clause taken into account in
the DB2 update orders
(C:028064)
"CURSOR FOR UPDATE" clause taken into account in the DB2
update orders for eBusiness elementary components.
Addition of a new CURSUPDT=YES option that can be defined
either at library level or at C/S Application level.
If this option is chosen, the SELECT SQL orders for update
are replaced by an OPEN CURSOR FOR UPDATE.

Availability of the separator option for data
elements defined with a date or time format
(C:028066)
The separator option for data elements defined with a date
format (E-M-G) or time format (T) is now available.
The separator must be entered on the second character of the
format field (input, internal, output).
Examples: M-,G/,E-,T: ....

New ERS operator for system errors in the
eBusiness module
(C:028081)
Programming of system errors in the eBusiness module.
The new ERS operator is available.
This operator sets a system error and a branch to the
program end is systematically generated (F81RE for the
components and in F97ER for the monitors and Folder
manager).

The format of manipulated dates is no more
required for the operations on dates
(C:028200)
The format of manipulated dates is no more required for
the operations on dates. The format of the data elements
declared as dates is automatically extracted from the
repository.

The storage capacity of SQL accesses is no more
limited to 1000 lines
(C:028201)
The storage capacity of SQL accesses is no more limited to
1000 lines.
It is possible to increase this capacity by authorizing
letters input in the line numbers of the -GG
(GENERATION ELEMENTS FOR SEGMENT) screen of segments.
The generation lines are V3-type lines and the line number
is now stored in an alphanumeric field.

IMS target: CBLTDLI calls replaced by CEETDLI
calls for a 'generated language' set to D
(C:028403)
Generation of calls to CEETDLI for IMS

All the calls to CBLTDLI are replaced by calls to CEETDLI
if the 'GENERATED LANGUAGE' of the generation library is
set to 'D'.

Generated programs

SQL Server: recognition of the DEFAULT clause for
the fields declared as NOT NULL.
(C:016539)
SQL Server: recognition of the DEFAULT clause for the
fields declared as NOT NULL.
For alphanumeric fields, the default value will be
NOT NULL DEFAULT ' ' ; for numeric fields, the default
value will be NOT NULL DEFAULT ZERO or, if a value is
indicated in the VALUE fields for the Data Elements called
in Segments, this value will be the default value
(same for the Q2, QG, QO, QP and QY type Blocks).
Moreover 'TS'-type Data Elements will be generated as
DATETIME instead of CHAR(00026) for SQL Server.

Addition of a field containing the Pacbase version
and the generator version in "Pacbase Constants".
(C:027492)
Creation of a field containing the Pacbase version and the
generator version.
Addition of 3 areas in the PACBASE constants:
05 RELEAS PICTURE X(7). -- version (ex : 3.5 V
05 DATGE PICTURE X(10). -- generator date
05 DATSQ PICTURE X(10). -- skeleton date
!! The CONSTANTS area goes up from X(60) to X(87)

New option for the generation of DB2 Segments in
the host variables
(C:027736)
A new generation option for DB2 Segments makes it possible
to include, in the hosts variables, all the Data Elements
called in the Segment.
This new option, DESCR=ALL, is to be entered on the
Generation Options (-GO) of Q2-type SQL Database Blocks.
This change is linked to the change 27735.

Monitor and Folder Manager: modification of the
work file management.
(C:027855)
Monitor and Folder Manager: modification of the work file
management.
There is a write access to the work file if:
- a user buffer is used,
- the request is sent via more than one message,
- the response causes a capacity overflow.
A record can then be created either in the Communication
Monitor or in the Folder.

Warining: this optimization requires the Communication
Monitor and the Folder managers linked to it ('eBusiness'
entity) to be generated again with this optimization.

Availability of the separator option for data
elements defined with a date or time format
(C:028066)
The separator option for data elements defined with a date
format (E-M-G) or time format (T) is now available.
The separator must be entered on the second character of the
format field (input, internal, output).
Examples: M-,G/,E-,T: ....

Integration of Large Object format for the DB2
and Oracle blocks generation
(C:028106)
Integration of Large Object format for the SQL
generation

- New type of data elements : L (Large Object)
* Usage 1 to 9 for DB2
* Usage 1 to 3 for Oracle
* call of L-type data element in a segment: the data element
is not taken into account in the length calculation,
occurs are fordidden.
- Generators: these data elements are taken into account for
Q2, QB and QP blocks.
01 variable-name
USAGE SQL TYPE IS BLOB (n/nK/nM/nG) usage '1'/DB2
USAGE SQL TYPE IS CLOB (n/nK/nM/nG) usage '2'/DB2
USAGE SQL TYPE IS DBCLOB (n/nK/nM/nG) usage '3'/DB2
USAGE SQL TYPE IS BLOB-LOCATOR usage '4'/DB2
USAGE SQL TYPE IS CLOB-LOCATOR usage '5'/DB2
USAGE SQL TYPE IS DBCLOB-LOCATOR usage '6'/DB2
USAGE SQL TYPE IS BLOB-FILE usage '7'/DB2
USAGE SQL TYPE IS CLOB-FILE usage '8'/DB2
USAGE SQL TYPE IS DBCLOB-FILE usage '9'/DB2
SQL-BLOB usage '1'/ORACLE
SQL-CLOB usage '2'/ORACLE
SQL-BFILE usage '3'/ORACLE

Generation

Variant capture is controlled
(C:024751)

When variants are updated (batch, dialog, dbd, dialog C/S,
eBusiness), they are controlled and limited to those
indicated in the "IBM Software Annoucement letter".

Database management

Administration entities can be deleted via the
ROAD/REOR procedure.
(C:028859)
Administration entities can be deleted via the
ROAD/REOR procedure.
You can request the physical deletion of the Adminstration
Database entities.
Command line:
Col 2 : E
Col 3 : Y
Col 4 (2 char.) : call type (AB= base, AU= User,...)
Col 6 (30 char.) : entity code (use of * character possible)

Additional controls:
Deleting an active key is impossible (either directly or in
a generic way).
Deleting the data related to the site's parameters table and
security (RACF, ..) is also impossible.

On-Line System Development

Variant capture is controlled
(C:024751)

When variants are updated (batch, dialog, dbd, dialog C/S,
eBusiness), they are controlled and limited to those
indicated in the "IBM Software Annoucement letter".

Addition of a field containing the Pacbase version
and the generator version in "Pacbase Constants".
(C:027492)
Creation of a field containing the Pacbase version and the
generator version.
Addition of 3 areas in the PACBASE constants:
05 RELEAS PICTURE X(7). -- version (ex : 3.5 V
05 DATGE PICTURE X(10). -- generator date
05 DATSQ PICTURE X(10). -- skeleton date
!! The CONSTANTS area goes up from X(60) to X(87)

New operator: MOVE CORRESPONDING between two
COBOL fields
(C:027731)
Definition of a new operator:
-----------------------------
MOVE CORRESPONDING between two Cobol group fields
Syntax: MCI OPERANDE1 OPERANDE2
A postprocessor has been developed and is included in
the new procedure BVPGPMC.
Implementation:
---------------
For any area of the Data Division of a program (Batch,
Online).
Result:
-------
A move is generated for each elementary area having the same
code in the 2 operands. The linking criterion corresponds
to the string behind the first '-'.
The occurs is taken into account if it is specified at the
operand level (A or/and 2).
Limits:
-------
Only one target (only one OPERANDE2).
No consistency control.
The picture is not taken into account.
"MOVE ZONE OF ZONEB" Cobol option not taken into account.

Parameterization of the DO operator counter
(C:027732)

Parameterization of the DO operator counter.
It is now possible to choose the variable which will
used as counter for the DO operator.
In the condition area, it is possible to define the name
of the index used in the DO loop. Addition of a parameter
in first position of the DO condition, coded as follows:
I=zoneind where 'zoneind' corresponds to a working area
declared by the user.

New condition types for date control: DV and DI
(C:027733)

New condition types to control the dates.
Processing under the condition of validity or invalidity
of a date. To do so, two new condition types have been
added:
DV: execution of the processing if the date specified in
the condition area is valid.
DI: execution of the processing if the date specified in
the condition area is not valid.
First character of condition area must be the date format
(ex : DV D datefield).

Date Data Elements can be broken down into
elementary fields.
(C:027735)
Data Elements with a date format can be broken down into
elementary fields which clearly represent the day, month
and year.
An option, BREAKDATE=YES, can now be entered in the
Generation Options (-GO) of:
- a Library,
- a Dialog,
- a C/S Application,
- a Program.
In a Program, the BREAKDATE=NO option can be entered in the
Generation Options (-GO) to avoid the breakdown of dates in
this particular Program, even if the option is set to
YES at the Library level.
NB: This option must be entered alone on a line and must
begin in column 1.

New option for the generation of DB2 Segments in
the host variables
(C:027736)
A new generation option for DB2 Segments makes it possible
to include, in the hosts variables, all the Data Elements
called in the Segment.
This new option, DESCR=ALL, is to be entered on the
Generation Options (-GO) of Q2-type SQL Database Blocks.
This change is linked to the change 27735.

Make it possible to call n SQL physical access
from description lines.
(C:027959)
Dialogue and Elementary Components: the purpose is to make
it possible to call SQL non-standard physical access, which
are partly described in the description lines of a Segment
representing a SQL table.
If the user has coded a sub-function, in a function F80,
with *C as a condition type and ffnn A1=S1 as a condition,
with A1 corresponding to a non-standard access described
in the Segment, and S1 corresponding to one of the
non-standard access which are taken into account by the
generator, then, the access generation is including the
information described by the user in the Segment.
They are completed by
other useful information such
as: the column name, the host-variable, the external name
of the table... depending on the standard access-type
defined.
For a DECLARE CURSOR (DC), the user is responsible for
positioning the clause WHERE (as for the Program entity).

New operator giving the difference between two
dates: DAD
(C:027960)
New operator giving the difference between two dates.
deux dates
Creation of the new operator DAD 'Date Difference'.
In the operand field, the syntax of the operation is as
follows:
xy ffnn-Date1 ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
The result is stored in an area, NUM-DAYS, automatically
declared in working.

New condition based on the comparison between two
dates: DC
(C:027961)
New condition based on the comparison between two dates.
Creation of the new condition type DC in the condition
field. The syntax is as follows:
xy ffnn-Date1 oper ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
oper corresponds to the comparison type and
can have the following values:
> or < or > = or < = or = or NOT > or NOT < or NOT=
If this condition type is assigned to a subfunction,
the comparison test must be followed by the processing:
NEXT SENTENCE ELSE GO TO Fffss-FN.

'C'-type Screens can call Elementary Components.
(C:027978)

Now a 'C'-type Screen (C/S Screen or TUI Client) can call
a 3.x Elementary Component.

Availability of the separator option for data
elements defined with a date or time format
(C:028066)
The separator option for data elements defined with a date
format (E-M-G) or time format (T) is now available.
The separator must be entered on the second character of the
format field (input, internal, output).
Examples: M-,G/,E-,T: ....

The format of manipulated dates is no more
required for the operations on dates
(C:028200)
The format of manipulated dates is no more required for
the operations on dates. The format of the data elements
declared as dates is automatically extracted from the
repository.

IMS target: CBLTDLI calls replaced by CEETDLI
calls for a 'generated language' set to D
(C:028403)
Generation of calls to CEETDLI for IMS

All the calls to CBLTDLI are replaced by calls to CEETDLI
if the 'GENERATED LANGUAGE' of the generation library is
set to 'D'.

Pacbase Access Facility

Now, it' s possible to access to the LOCK table
thru the LL choice.
(C:007569)
Now, it's possible to access to the LOCK table thru the LL
choice.

PAF: Creation of a new table to extract timestamp
data.
(C:027144)
PAF: A new table enables you to extract the timestamp data,
with a possible selection on its contents.

This table cannot be updated.
This table code is TIMESTAMP. It contains the following
fields: TENT X(3), entity type, CENT X(30), entity code,
CUSU X(8), user code which modified the entity,
ODAT X(8), OTIM X(6), timestamps of the modified entity,
CSES 9(4), TSES X, session.
For access reasons, you must simultaneously select
an entity type and an entity code (the presence of both
conditions is checked).
If you select only an entity code, the 'CO3' error will be
generated.
An access to the TIMESTAMP Table does not correspond to one
index type only ; so, for example, to extract all
the timestamps of the Program-type entities, you are advised
to do the following:
Break down your request in two parts (with embedded cursors)
EXEC PAF DECLARE CU00 CURSOR FOR
SELECT * FROM PGMDEF WHERE
CPGM 'P '
END-EXEC
and then EXEC PAF DECLARE CU01 CURSOR FOR
SELECT * FROM TIMESTAMP WHERE
TENT = 'PGM'
AND CENT = CU00-CPGM
END-EXEC
You can also make a selection on the other fields (user code
session...).

PAF: Extraction of the extension User Entities
supplied with selection on the short code
(C:028027)
PAF: Extraction of the extension User Entities supplied
with selection on the short code
You can request the extraction of Elementary Component-type
or eBusiness-type extension User Entities with a condition
on the short code:
. Elementary Component YCEDEF - WHERE CCEIDE = ........
. eBusiness entity YCSDEF - WHERE CCSIDE = ........
. Folder YDODEF - WHERE CCOIDE = ........
etc...
The Data Element code which corresponds to the short code
is found on the description 00 of the Meta-Entity.

The return code of a PAF connection is more
precise and better documented.
(C:028217)
The return code of a connection via PAF can be one of the
following ones:
45 : Unknown user code
46 : Erroneous password
47 : Erroneous application code
48 : Erroneous session number
49 : Missing user code

Batch Procedures

Batch update: the deletion by mistake of a line
generates a warning
(C:028408)
In batch update, the deletion by mistake of a line
generates a warning.

Administration entities can be deleted via the
ROAD/REOR procedure.
(C:028859)
Administration entities can be deleted via the
ROAD/REOR procedure.
You can request the physical deletion of the Adminstration
Database entities.
Command line:
Col 2 : E
Col 3 : Y
Col 4 (2 char.) : call type (AB= base, AU= User,...)
Col 6 (30 char.) : entity code (use of * character possible)

Additional controls:
Deleting an active key is impossible (either directly or in
a generic way).
Deleting the data related to the site's parameters table and
security (RACF, ..) is also impossible.

Batch procedure to manage use rights assignment
(UKD1).
(C:028934)
New batch procedure to manage use rights.
This procedure has two functions:
- Assign use rights to a group of users
- Activate a new access key
User input:
. Identification line with administrator user code
and password.
. K-line to activate an access key
('K' followed by the 14-characters access key identifier)
-- the key must already be defined in the database.
. U-line to modify or assign use rights (optional)
("UusercodeTYP1xTYP2xTYP3x etc.")
TYPn (4 characters) is the type of use right to be assigned
(maximum of 10 seats by line) :
CO1 : Designer
IW1 : Developer for Developer workbench
PA1 : Text User Interface for VA Pac in character-mode.
LE1 : Reader
T1n : Traditional build facility Mono-target n
T2n : Traditional build facility Bi-target n
TM1 : Traditional build facility Multi-target
E1n : eBusiness build facility Mono-target n
E2n : eBusiness build facility Bi-target n
EM1 : eBusiness build facility Multi-target
The x characters corresponds to the permanent assignment
of the right (1 if permanent).

The transactions generated after the use rights
modifications will take into account the possible new
access key.
Therefore the modification of the access key must be entered
before the U-line(s).

Caution: this procedure updates the administration database,
the files must be closed to online use.

Retrieve

PEI retrieval: with an option, les environments
are created in inter-library
(C:029323)
PEI retrieval: with an option, the environments are created
in inter-library if, on the user identification line
(*-line) of the PEI retrieval (PP25), the inter-library is
specified ('***' in the application area of the line,
position 19 to 21).
The environments and their application are created in
inter-library and in 0001Z session.

Software Config. Management

LEG screen: direct access to an instance, update
and help screen.
(C:029001)
SCM: update on the LEG screen.
(see also c27192)
The list of the generated entities can be viewed in TP mode.
To access this list, enter the following value in the CHOICE
field:
CH: LEG.............
The LEG value may be followed by:
. The short code of an environment, on 2 characters.
. An entity type, on 1 to 3 characters: P (Program), O
(Screen), B (Database Block), D (COPY book), YCS (eBusiness
Application), YDO (Folder), YSI (Initialization Server),
YMC (Communication Monitor), or YCE (Elementary Component).
. An application code, on 10 characters.
. The external name of an instance, on 8 characters.

Blanks must be replaced with '&':
Ex : LEGDEP&&DEFAUL&&&TEXTNAM&&
where 'DE' is the environment code, 'P' the entity type,
'DEFAULT' the application code and 'EXTNAM' the external
name.
By default, the first environment found and the Program
entity are displayed.
You can display an instance by entering its external
name (EXTNAM) in the choice field.
You can scroll through all the applications of a given
environment.
You can access a second entity type via the choice field
only.
The same instance will be displayed as many times as it has
been put into production.

POSSIBLE UPDATES ON THE 'LEG' SCREEN
------------------------------------
. TRANSFER OF INSTANCES
A transfer requires that the target environment be
associated with the entity type of the instance to be
transferred.
To transfer one or more instances, overtype the environment
and/or the application. Enter the 'E' action code on the
lines which are not to be transferred.
If all the instances displayed on the screen are to be
transferred, just overtype the environment and/or the
application and press the ENTER key.
NOTE: A transfer does not delete the instance in the source
environment.
The target environment is considered as a production
environment. Two cases are possible:
* The instance to be transferred is already in production.
The date and number of the production session are
transferred.
* The instance to be transferred is not in production.
In this case, the production information is not
transferred.
Production turnover information will be filled in
automatically only when the instance is actually put into
production (HIPM execution).
. DELETION ('D' action code):
You can delete instances of any entity type, whether they
are in production or not. However, use this action code
with caution...
. MODIFICATION ('M' action code):
You can reset the production turnover information of an
instance. This information will be updated the next time
the instance will be put into production.
If you manually put an instance into production from
the LEG screen, an 'M' will be displayed in the
'Production Turnover Mode' field.

SCREEN HELP:
-----------
Help on screen: enter '?' in the action code field, and
press the ENTER key.
Help on input fields: enter '?' in the input field and press
PF4.

PEI retrieval: with an option, les environments
are created in inter-library
(C:029323)
PEI retrieval: with an option, the environments are created
in inter-library if, on the user identification line
(*-line) of the PEI retrieval (PP25), the inter-library is
specified ('***' in the application area of the line,
position 19 to 21).
The environments and their application are created in
inter-library and in 0001Z session.

A help screen is available on the LEG screen.
(C:029351)

A help screen is available on the LEG screen.

Production turnover actions are now displayed
in a journal
(C:029641)
New functionality of the SCM module

All the production turnover actions are displayed in a
journal, which can be viewed in character mode (LEG choice).
Refer to the Administrator documentation for more details.

SQL Langage

SQL Server: recognition of the DEFAULT clause for
the fields declared as NOT NULL.
(C:016539)
SQL Server: recognition of the DEFAULT clause for the
fields declared as NOT NULL.
For alphanumeric fields, the default value will be
NOT NULL DEFAULT ' ' ; for numeric fields, the default
value will be NOT NULL DEFAULT ZERO or, if a value is
indicated in the VALUE fields for the Data Elements called
in Segments, this value will be the default value
(same for the Q2, QG, QO, QP and QY type Blocks).
Moreover 'TS'-type Data Elements will be generated as
DATETIME instead of CHAR(00026) for SQL Server.

"CURSOR FOR UPDATE" clause taken into account in
the DB2 update orders
(C:028064)
"CURSOR FOR UPDATE" clause taken into account in the DB2
update orders for eBusiness elementary components.
Addition of a new CURSUPDT=YES option that can be defined
either at library level or at C/S Application level.
If this option is chosen, the SELECT SQL orders for update
are replaced by an OPEN CURSOR FOR UPDATE.

Integration of Large Object format for the DB2
and Oracle blocks generation
(C:028106)
Integration of Large Object format for the SQL
generation

- New type of data elements : L (Large Object)
* Usage 1 to 9 for DB2
* Usage 1 to 3 for Oracle
* call of L-type data element in a segment: the data element
is not taken into account in the length calculation,
occurs are fordidden.
- Generators: these data elements are taken into account for
Q2, QB and QP blocks.
01 variable-name
USAGE SQL TYPE IS BLOB (n/nK/nM/nG) usage '1'/DB2
USAGE SQL TYPE IS CLOB (n/nK/nM/nG) usage '2'/DB2
USAGE SQL TYPE IS DBCLOB (n/nK/nM/nG) usage '3'/DB2
USAGE SQL TYPE IS BLOB-LOCATOR usage '4'/DB2
USAGE SQL TYPE IS CLOB-LOCATOR usage '5'/DB2
USAGE SQL TYPE IS DBCLOB-LOCATOR usage '6'/DB2
USAGE SQL TYPE IS BLOB-FILE usage '7'/DB2
USAGE SQL TYPE IS CLOB-FILE usage '8'/DB2
USAGE SQL TYPE IS DBCLOB-FILE usage '9'/DB2
SQL-BLOB usage '1'/ORACLE
SQL-CLOB usage '2'/ORACLE
SQL-BFILE usage '3'/ORACLE

The storage capacity of SQL accesses is no more
limited to 1000 lines
(C:028201)
The storage capacity of SQL accesses is no more limited to
1000 lines.
It is possible to increase this capacity by authorizing
letters input in the line numbers of the -GG
(GENERATION ELEMENTS FOR SEGMENT) screen of segments.
The generation lines are V3-type lines and the line number
is now stored in an alphanumeric field.

Procedural language

New operators: MC (Move Corresponding) and
MF (Move Function)
(C:022585)
Definition of two new operators:
- MC for Move Corresponding
Syntax: MC ident1 ident2
Generated code: MOVE CORR ident1 TO IDENT2
- MF for Move Function
Syntax: MF 'function' (parameter1) parameter2
Generated code: MOVE FUNCTION 'function' (parameter1) TO
parametre2
'function' is one of Cobol intrinsec functions such as
UPPER-CASE.

New operator for operations on dates: DAO
(C:027734)

New operator for operations on dates: DAO.
This operator is used to add or substract a number of days
to the variable declared in date format in the repository.
Syntax :
DAO x snnnn date1
x = date format
s = '+' or '-'
nnnn = number or numeric field
date1 = Input and output date field

New operator giving the difference between two
dates: DAD
(C:027960)
New operator giving the difference between two dates.
deux dates
Creation of the new operator DAD 'Date Difference'.
In the operand field, the syntax of the operation is as
follows:
xy ffnn-Date1 ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
The result is stored in an area, NUM-DAYS, automatically
declared in working.

New condition based on the comparison between two
dates: DC
(C:027961)
New condition based on the comparison between two dates.
Creation of the new condition type DC in the condition
field. The syntax is as follows:
xy ffnn-Date1 oper ssnn-Date2
where xy corresponds to the format of the two dates
specified behind
oper corresponds to the comparison type and
can have the following values:
> or < or > = or < = or = or NOT > or NOT < or NOT=
If this condition type is assigned to a subfunction,
the comparison test must be followed by the processing:
NEXT SENTENCE ELSE GO TO Fffss-FN.

CORRECTED BUGS

Administration

The management and the generation of DMS II
Database Blocks are now authorized.
(C:030059)
The management and the generation of DMS II
Database Blocks are now authorized.
You can now enter '20' in the Block type for DMSII
and generate for a 'DMSII' target.

Folder COBOL API

Cobol API in an eBusiness component :
Ffolder-ENTRY label is missing.
(C:028305)
Cobol API in an eBusiness component : Ffolder-ENTRY label
was missing. This is now corrected.
The generated F93EZ-FN label was useless.
It will not be generated anymore.

Batch

Gaps were wrongly created if an error was detected
when User Entities were updated.
(C:028722)
Gaps were wrongly created if an error was detected
when User Entities were updated.
When checking the authorization for the creation of the User
Entity Definition according to the duplicates found in the
higler-level and lower-level libraries, gaps were created
and the U.E. could not be used.
This has been corrected.
Warning: the index management has been modified.
A reorganization is required for the administration database
(ROAD) and development databases (REOR).
The reorganization must be run before the installation of
the model (D08META and I05META).

Batch System Development

Generation with BREAKDATE option
Field to be broken down on level 01
(C:028222)
Batch generator:
If the field to be broken down is on a level 01 (margin A)
the generated levels will be set to margin B in cobol.

Alignment of the batch generation of SSA secondary
indexes with the on-line generation
(C:028381)
Batch Generation of SSA - IMS DL/1

GCP / DL/1 segment:
If a Data Element is found in the Segment with a numeric
character, the Data Element generated in the SSA is preceded
by an 'X'
ex : ...;
09 filler picture x(9) value '(XELEM '.
....

Batch generation: Common parts wrongly mixed
(C:028834)

This change replaces the change 26849 (GCP KO if -CD with
an empty continuation line and breaks on the first line).
Corrected.

Refused generation: error 1737 (inadequate
authorizations)
(C:028874)
The generation is now possible in the batch generator.
There was an incorrect initialization on some systems.
Corrected.

The 'VALUE' clause is no longer generated for occursed
fields for a BULL-GCOS7 target.
(C:029378)
The 'VALUE' clause is no longer generated for occursed
fields if the 'type of COBOL to generate' is 4 (Bull-Gcos7).

The selected sub-schemas are recognized when
calling an SQL Data Structure in the -W screen
(C:029410)
The selected sub-schemas are recognized when
calling an SQL Data Structure in the -W screen
The sub-schema is now recognized for the generation of
SQL statements.

Generation of AD2 operator if 'code for sequence
of generation' is other than the Program code.
(C:029483)
Generation of the AD2 operator when the 'code for sequence
of generation' is different from the Program code.
The AD2 operator is now correctly generated, even if the
'code for sequence of generation' of the Program is
different from the Program code.

SQL generation error if Segment on a -CD cont'.
line and Block code not indicated in EXTERNAL NAME
(C:029704)
SQL generation error if the Segment was called on a
continuation line of a Program -CD and if the Block name
was not repeated in the EXTERNAL NAME field.

Now if a DB2 Segment is called in a Program -CD on a
continuation line, and if the Block name (in EXTERNAL NAME)
is entered only on the main line, the SQL statements will
be correctly generated.

DESCR=ALL: Group Data Elements are recognized
for host variables only
(C:030016)
DBD Block, DESCR=ALL: Group Data Elements are recognized,
except in SQL statements and in SQL indicators.
The DESCR=ALL option allows the recognition of group
Data Elements in a DB2 Block, when these groups are
constituted of elementary Elements (Change 27736).
Now a group Data Element can also be constituted of
other group Data Elements. This applies to the Segment
which describes the table but neither to the indicators
(V-ffnn) nor to the SQL statements.

GCP: Segment with an initial value
(C:030067)

GCP: Segment with an initial value

The Programs which contain Segments with initial values are
correctly generated.

Errors in the generation of a Program in
'Cobol Source' (-9)
(C:030149)
Errors in the generation of a Program in
'Cobol Source' (-9)

1) Generation of a Programme (P) in 'Cobol Source' (-9)
with the option for the suppression of Cobol numbering.
With the Change 27735 (breakdown of dates), extraneous lines
may wrongly appear in a Program written in lines 9 with the
'suppression of Cobol numbering' option.
This has been corrected.

2) Generation of a Program (P) in 'Cobol Source' (-9)
with a '/' in column 7
This '/' line is replaced, in the generated code, with
extraneous lines.
This has been corrected: the '/' line remains as is in
the generated code.

Data Element with a TimeStamp type (TS) was
wrongly generated with a length of 8 instead of 26
(C:030170)
A Data Element with a TS type (Timestamp) was wrongly
generated with a length of 8 instead of 26.
This has been corrected.

Key, license

Error 1743E - GENERATION REFUSED: MAXIMUM NUMBER
OF RIGHTS IS REACHED for a permanent right
(C:029082)
The error 1743E - GENERATION REFUSED: MAXIMUM NUMBER OF
RIGHTS IS REACHED was erroneously generated for a user
having a permanent right, when the maximum number of
connections of users without permanent right was reached.
Corrected.

Amélioration de la procédure UKD1
(C:029443)

Additional control:
Assigning rights to a group of users ('U' line) and
activating a new key ('K' line) cannot be done in the same
flow.

Warning: assigning a key is possible only if the perimeter
of this new key is identical to that of the old key.

Connection

User connections no longer modify
timestamp on access key and user updates.
(C:028640)
User connections no longer modify
timestamp on access key and user updates.

Management of errors on the VA Pacbase sign-on
screen
(C:029361)
VA Pacbase sign-on screen: the numericity control on the
session is now correctly performed.

Client/Server system develop.

Generation of Client/Server and eBusiness error
messages on two different files
(C:027952)
Generation of Client/Server and eBusiness error messages on
two different files.
************* COMPATIBILITY ************
The error messages of eBusiness Folder and Client/Server
components are not generated on the same files anymore.
The programs of the GPRT stream are:
PACK3S, PACK8S and PACK9S
The input and output files are:
- PAC7LM: error messages file to be updated.
- PAC7GM: new error messages file created during the
GPRT stream execution.
- PAC7IO: generation output report.
Those files respectively correspond to the PAC7LK, PAC7GK
and, PAC7IK files for the GEC commands.

eBusiness communication monitor and SQL work file:
LOCK TABLE deletion
(C:028128)
eBusiness communication monitor and SQL work file:
modification of the writing management on this file in
order to not have LOCK TABLE.

Warning: this modification results in the modification of
the generated Cobol source.

Initialization of the CENTUR area to 20
(C:029149)

For the generation of dialog program, C/S component or
eBusiness component, the CENTUR area is now initialized
to '20' instead of '19'.

NonStop SQL: generation of SQL orders for
DATE-type data elements
(C:029160)
NonStop SQL: the generation of SQL orders for DATE-type
data elements was not correct.
'àTYPE AS ...' was generated instead of 'TYPE AS ...'.
This has been corrected.

The 'VALUE' clause is no longer generated for occursed
fields for a BULL-GCOS7 target.
(C:029378)
The 'VALUE' clause is no longer generated for occursed
fields if the 'type of COBOL to generate' is 4 (Bull-Gcos7).

Erroneous generation of CALL for IMS sub-monitors
(CALL '......').
(C:029492)
Generation of IMS submonitor: some CALL were wrongly
generated with CALL '......'. This has been corrected.
It is now generated as CALL 'CBLTDLI' for a 'C'-type
generated language, or CALL 'CEETDLI' for a
'D'-type generated language.

Generation of a Folder with an 'F' type of code
with extract method called in a Macro-Structure.
(C:029514)
Generation of a Folder with an 'F' type of code with
extract method called in a Macro-Structure.

The extract method is generated in the Folder if it is
called by a Macro-Structure and if the call to this
Macro-Structure is specified in two different libraries.

The NUVERS generation option of an Application
Component now contains 5 characters.
(C:030004)
The NUVERS generation option of an Application
Component now contains 5 characters.

Erroneous generation of CALL for IMS sub-monitors
(CALL '......').
(C:030065)
Generation of IMS submonitor: some CALL were wrongly
generated with CALL '......'. This has been corrected.
It is now generated as CALL 'CBLTDLI' for a 'C'-type
generated language, or CALL 'CEETDLI' for a
'D'-type generated language.

Data Element with a TimeStamp type (TS) was
wrongly generated with a length of 8 instead of 26
(C:030170)
A Data Element with a TS type (Timestamp) was wrongly
generated with a length of 8 instead of 26.
This has been corrected.

Client/Server system dev. 3.x

Generation of Client/Server and eBusiness error
messages on two different files
(C:027952)
Generation of Client/Server and eBusiness error messages on
two different files.
************* COMPATIBILITY ************
The error messages of eBusiness Folder and Client/Server
components are not generated on the same files anymore.
The programs of the GPRT stream are:
PACK3S, PACK8S and PACK9S
The input and output files are:
- PAC7LM: error messages file to be updated.
- PAC7GM: new error messages file created during the
GPRT stream execution.
- PAC7IO: generation output report.
Those files respectively correspond to the PAC7LK, PAC7GK
and, PAC7IK files for the GEC commands.

eBusiness communication monitor and SQL work file:
LOCK TABLE deletion
(C:028128)
eBusiness communication monitor and SQL work file:
modification of the writing management on this file in
order to not have LOCK TABLE.

Warning: this modification results in the modification of
the generated Cobol source.

Generation of eBusiness entities with the same
short code.
(C:028129)
You can now generate, in the same run, the entities of the
eBusiness module which have different types (CE, DO,..) but
the same short code.

The IMS/DB2 communication monitor returns the
IPCB code instead of the SQLCODE in some cases
(C:028152)
IMS/DB2 communication monitor: in case of error, the IPCB
code was returned instead of the SQLCODE.
IMS communication monitor and DB2 work file: in case of
error on the work file, the IPCB code was erroneously
returned instead of the SQLCODE.
Corrected.

Cobol API in an eBusiness component :
Ffolder-ENTRY label is missing.
(C:028305)
Cobol API in an eBusiness component : Ffolder-ENTRY label
was missing. This is now corrected.
The generated F93EZ-FN label was useless.
It will not be generated anymore.

Deletion of useless lines concerning the SQL under
UNISYS 2200 for a communication monitor
(C:028390)
A new option SUPSQL=YES is added at eBusiness application
level.
When this option is selected, the excessive SQL orders are
not generated.

Error SCH1 for a creation on a component with
cascade deletion
(C:028735)
eBusiness component with cascade deletion:
The SCH1 error was sent for a creation.
Corrected.

Unisys monitor: management of BEGIN and END THREAD
orders
(C:028768)
Unisys monitor: management of BEGIN and END THREAD orders.
The EXEC SQL BEGIN THREAD FOR UDSSRC order is moved to the
beginning of the procedure division.
The END THREAD order is conditioned in order to be executed
once only.

Initialization of the CENTUR area to 20
(C:029149)

For the generation of dialog program, C/S component or
eBusiness component, the CENTUR area is now initialized
to '20' instead of '19'.

Generation of the folders table for a TANDEM
communication monitor
(C:029158)
The generation of the folders table was not complete
for a TANDEM communication monitor.
The folders table contained the first folder only.
This has been corrected.

NonStop SQL: generation of SQL orders for
DATE-type data elements
(C:029160)
NonStop SQL: the generation of SQL orders for DATE-type
data elements was not correct.
'àTYPE AS ...' was generated instead of 'TYPE AS ...'.
This has been corrected.

Tandem Pathway: generation of calls to CRE
library functions instead of the C85 lib. ones.
(C:029161)
Tandem Pathway: generation of calls to the functions of the
Common Runtime Environment library instead of the Cobol 85
library.

Correct generation of the multi-transactions files
used as POT in an elementary component
(C:029208)
Correct generation of the multi-transactions files used as
POT in an elementary component.

If a specific part of a file containing a common part is
used as POT in an elementary component, the common part
of the file (nn00) is correctly generated in the File
Section (and not in Working).

Source insertion via *A and/or *P on a Data Elem.
The number of generated lines can be up to 1260.
(C:029294)
Source insertion via *A and/or *P on a Data Element.
The limit in the number of generated lines is now 1260.

Moreover when the limit of 1260 lines is reached, an error
is sent to PAC7ID.

Elementary Component: Logical View managed
with different types of Persistency Objects.
(C:029403)
The logical access to a Logical View, in a read operation,
was not correct if the main Persistency Object was of
relational or DL1 type
and if there was a secondary Persistency Object
with a different type.
The error has been corrected.

The FST variable in F80-SEGT-P is set to '0'
and then reset to '1' in F80-SEGT-CL
(C:029640)
When an Elementary Component is generated, the
FFNN-FST variable is now set to '0' for an
OPEN curor and to '1' for a CLOSE cursor.

GMS: generation of an Elementary Component:
Transfer of a View data
(C:029866)
GMS: generation of an Elementary Component:
Transfer of a View data

Each data item of a Logical View is now transferred only
once (and no longer as many times as the extraction
parameter of the method is used).
(Function FXXXX-TRVW-CATR: function for the transfer of
data of the XXXX View)

Database Block (DDL)

CH: B......DH - the deletion of a -DH is not
possible if there is an associated documentation
(C:028791)
On a database block, the deletion of a '-DH' is not
authorized if there is an associated documentation.

Design

Modification of the methodology parameters in the
BVPAE file
(C:029987)
The methodology parameters file (BVPAE) has been modified in
order to correctly manage the cross-references to entities
whose codes are shorter than 6 characters long (Report,
Segment).
The BVPAE file must be re-loaded.

Dictionary

The deletion of a DS call line in a program did
not delete the cross-references
(C:028213)
In a batch program, when a call line of data structures is
deleted, the references are correctly deleted.

In an erroneous context, the rejected transactions
management and printing may be incorrect
(C:028501)
In case of erroneous context, the management and printing of
the rejected transactions may be incorrect.
According to the context, rejected lines might have been
printed several times and the transactions file did not
contain all the rejected transactions.
This is now corrected.

The Reorganization linked to the 3.0 - 3.5V01
upgrade can corrupt the database
(C:028673)
If the reorganization linked to the 3.5 V01 version upgrade
was not done, problems may occur in the following
reorganization.
This modification avoids these problems.

Gaps were wrongly created if an error was detected
when User Entities were updated.
(C:028722)
Gaps were wrongly created if an error was detected
when User Entities were updated.
When checking the authorization for the creation of the User
Entity Definition according to the duplicates found in the
higler-level and lower-level libraries, gaps were created
and the U.E. could not be used.
This has been corrected.
Warning: the index management has been modified.
A reorganization is required for the administration database
(ROAD) and development databases (REOR).
The reorganization must be run before the installation of
the model (D08META and I05META).

A user cannot delete an entity having a technical
lock
(C:028996)
An entity downloaded in the Workstation for an update cannot
be deleted, even by the user who has downloaded it.

Impact of macros' modification on calling
programs that have an inferior internal code
(C:029334)
A modification in a macrostructure called by a program
that has an internal code inferior to the macro's one is
correctly passed in the calling program.
As a sample, after the deletion of a -P line in the
macrostructure, the deleted line does not appear in the
calling program.

Synonyms can be updated in the thesaurus.
(C:029988)

Synonyms can be updated in the thesaurus.

Invalid indexes were created upon the update.
Indexes are now correctly formatted.

Reconstitution of the x-references for User
Entities
(C:030032)
If the description of a Meta Entity has been moved to a
higher-level library (deletion and then creation in the
same session number), the indexes of the corresponding
User Entities are correctly reconstituted by the
reorganization procedure (REOR).
A reorganization must then be run to make this correction
effective.

eBusiness Module

The request for the deletion of a Folder also
deletes all its dependencies (descriptions).
(C:028097)
The request for the deletion of a Folder also deletes all
its dependencies, i.e. comments or descriptions.
If all its dependencies are in the same library as the
Definition, the deletion is immediate.
If one of its dependencies is in a lower-level library, a
message warns you of its existence and prompts you to
confirm the deletion. In this case, all the dependencies are
then deleted (in the selection library and in the
lower-level library).

Deleting/creating a persistency object used to
trigger the error 'PERSISTENCY OBJECTS PRESENT'.
(C:028685)
The non-existence of the persistency object in the dynamics
of an Elementary Component is checked when the instance is
processed and not globally (when all the instances have been
checked) because the database may have been updated.

The deletion of an eBusiness module's entity
does no more generate an error
(C:029152)
The deletion of an eBusiness module's entity that has
depending elements (ex: a logical view containing data
elements) is now made without error.

Definition of eBusiness Application: possibility
to validate the server buffer deletion
(C:029176)
On the definition tab of an eBusiness Application, it is
now possible to validate the server buffer deletion.

Data Element

LNE choice: display with option C2
(C:029191)

In option C2, the choice LNE displays correctly the code
of a Data Element, the code of the Parent Data Element
and the usage.

Personalization

A PAF extractor retrieves all the data included
in the requested description
(C:029312)
PAF extractor on User Entities
All the data of the requested description is retrieved
by the extractor, whichever the length of the
description is.

Generators

Generation of Client/Server and eBusiness error
messages on two different files
(C:027952)
Generation of Client/Server and eBusiness error messages on
two different files.
************* COMPATIBILITY ************
The error messages of eBusiness Folder and Client/Server
components are not generated on the same files anymore.
The programs of the GPRT stream are:
PACK3S, PACK8S and PACK9S
The input and output files are:
- PAC7LM: error messages file to be updated.
- PAC7GM: new error messages file created during the
GPRT stream execution.
- PAC7IO: generation output report.
Those files respectively correspond to the PAC7LK, PAC7GK
and, PAC7IK files for the GEC commands.

Generation of eBusiness entities with the same
short code.
(C:028129)
You can now generate, in the same run, the entities of the
eBusiness module which have different types (CE, DO,..) but
the same short code.

Generation with BREAKDATE option
Field to be broken down on level 01
(C:028222)
Batch generator:
If the field to be broken down is on a level 01 (margin A)
the generated levels will be set to margin B in cobol.

Deletion of useless lines concerning the SQL under
UNISYS 2200 for a communication monitor
(C:028390)
A new option SUPSQL=YES is added at eBusiness application
level.
When this option is selected, the excessive SQL orders are
not generated.

SQL Block Description: the number of lines
recognized upon generation has been increased.
(C:028615)
In the 'Generation Elements' screen (-DRnnnGG) of an SQL
Database Block Description, the total number of lines
entered in each group (between
'... INSERTION BEGINNING < ---' and '... INSERTION END < ---')
and recognized upon generation has increased from 100 to 200.

SQL non standard access: if group data element in
a segment, preceding data element sent twice
(C:028759)
SQL non standard access: if an SQL table contains a group
data element, the data element which precedes this group
data element is sent twice. If it is the first data element
of the segment and if there is another segment before, the
last data element of the preceding segment is also sent.
Corrected.

Non assigned macro containing SQL orders
(not all) == incorrect generation
(C:028767)
Non assigned macro containing SQL orders.
The processings of this macrostructure are now correctly
assigned on the calling program.

Batch generation: Common parts wrongly mixed
(C:028834)

This change replaces the change 26849 (GCP KO if -CD with
an empty continuation line and breaks on the first line).
Corrected.

Refused generation: error 1737 (inadequate
authorizations)
(C:028874)
The generation is now possible in the batch generator.
There was an incorrect initialization on some systems.
Corrected.

GPRT: The return codes are now correctly
transmitted to the procedure
(C:028880)
As a result of the modification of the physical accesses
management, some return codes were not correctly transmitted
to the procedure.
This has been corrected.

Generation of the folders table for a TANDEM
communication monitor
(C:029158)
The generation of the folders table was not complete
for a TANDEM communication monitor.
The folders table contained the first folder only.
This has been corrected.

Generation of screen with PCB call: erroneous
error message
(C:029178)
Generation of screen with DL1 database: the control of
the database is correctly performed.

Correct generation of the multi-transactions files
used as POT in an elementary component
(C:029208)
Correct generation of the multi-transactions files used as
POT in an elementary component.

If a specific part of a file containing a common part is
used as POT in an elementary component, the common part
of the file (nn00) is correctly generated in the File
Section (and not in Working).

The GPMC post-processor for MCI can process more
than one program in one run only.
(C:029255)
The GPMC post-processor for the MCI operator
(MOVE CORRESPONDING) can process more than one program in
one run only.

Breakdate=yes : Breakdown is KO in two cases.
(C:029289)

Breakdate=yes : Breakdown is KO in two cases.

1. Dialog generation: When a Segment is called in WORKING
on an F-type line and with an S or E format, the date
breakdown into elementary fields
in the generated Segment is performed. However, the
internal format is taken into account instead of the output
or external format. This is now corrected.

2. Batch generation: When a Segment is called in WORKING
on an F-type line, the date breakdown into elementary fields
is not performed if the Program's Data Structure Calls tab
is empty.

Better management of the generation targets.
(C:029370)

Better management of the generation targets.

'C' type of code to generate:
The 'C' type has been added to Programs.
To submit a GCP with a 'C' type, you must have any
'traditional' build facility use right.
(no control of targets).

Fewer constraints for the generation of Screens with a
'3' or 'Q' type of code to generate: the type of code to
generate is no longer controlled for the transactional
monitor.

MCI operator: all the 'MOVE' will be generated,
even on occursed fields.
(C:029517)
The MCI operator generates a series of 'MOVE' on all the
fields which have the same code, from one group to another
group.
In this context, if one of the operands includes an index,
this index '(nn)' will be generated for all the fields of
this operand.

GPRT: unknown line codes are no longer ignored
but reported to the user.
(C:029608)
GPRT: the lines which are not recognized by the procedure
(lines other than 'Z', '*', or +AG) were simply ignored.
Now they are rejected and reported in an error message.

The management and the generation of DMS II
Database Blocks are now authorized.
(C:030059)
The management and the generation of DMS II
Database Blocks are now authorized.
You can now enter '20' in the Block type for DMSII
and generate for a 'DMSII' target.

Generated programs

eBusiness communication monitor and SQL work file:
LOCK TABLE deletion
(C:028128)
eBusiness communication monitor and SQL work file:
modification of the writing management on this file in
order to not have LOCK TABLE.

Warning: this modification results in the modification of
the generated Cobol source.

The IMS/DB2 communication monitor returns the
IPCB code instead of the SQLCODE in some cases
(C:028152)
IMS/DB2 communication monitor: in case of error, the IPCB
code was returned instead of the SQLCODE.
IMS communication monitor and DB2 work file: in case of
error on the work file, the IPCB code was erroneously
returned instead of the SQLCODE.
Corrected.

Cobol API in an eBusiness component :
Ffolder-ENTRY label is missing.
(C:028305)
Cobol API in an eBusiness component : Ffolder-ENTRY label
was missing. This is now corrected.
The generated F93EZ-FN label was useless.
It will not be generated anymore.

Alignment of the batch generation of SSA secondary
indexes with the on-line generation
(C:028381)
Batch Generation of SSA - IMS DL/1

GCP / DL/1 segment:
If a Data Element is found in the Segment with a numeric
character, the Data Element generated in the SSA is preceded
by an 'X'
ex : ...;
09 filler picture x(9) value '(XELEM '.
....

Error SCH1 for a creation on a component with
cascade deletion
(C:028735)
eBusiness component with cascade deletion:
The SCH1 error was sent for a creation.
Corrected.

Unisys monitor: management of BEGIN and END THREAD
orders
(C:028768)
Unisys monitor: management of BEGIN and END THREAD orders.
The EXEC SQL BEGIN THREAD FOR UDSSRC order is moved to the
beginning of the procedure division.
The END THREAD order is conditioned in order to be executed
once only.

In the SQL orders, the format of data elements
having an extended date format is no more truncate
(C:029068)
In the SQL orders, the format of data elements
having an extended date format is no more truncated.
In the generated F80 functions, some lines associated with
data elements having an extended date format specified on
their 'element description' screen might be truncated.
This has been corrected.

NonStop SQL: generation of SQL orders for
DATE-type data elements
(C:029160)
NonStop SQL: the generation of SQL orders for DATE-type
data elements was not correct.
'àTYPE AS ...' was generated instead of 'TYPE AS ...'.
This has been corrected.

Tandem Pathway: generation of calls to CRE
library functions instead of the C85 lib. ones.
(C:029161)
Tandem Pathway: generation of calls to the functions of the
Common Runtime Environment library instead of the Cobol 85
library.

All the relational names are recognized when
SQL accesses are generated
(C:029283)
All the relational names are recognized when SQL accesses
are generated:
- All the 'SQL-Data Element' entered on a Segment -GG
are replaced with all their relational names and not only
with their first relational name.

Source insertion via *A and/or *P on a Data Elem.
The number of generated lines can be up to 1260.
(C:029294)
Source insertion via *A and/or *P on a Data Element.
The limit in the number of generated lines is now 1260.

Moreover when the limit of 1260 lines is reached, an error
is sent to PAC7ID.

GCO - The initial value is now recognized for a
Data Element displayed and protected on the screen
(C:029304)
GCO - The initial value is now recognized for a
Data Element displayed and protected on the screen

In a Screen description (-CE with a C2 option), if you enter
an initial value for a displayed and protected Data Element
(nature 'F'), the loading of the initial value is generated
in the 'O-' in F8115.
!!! The BMS bitmap is not changed !!!

The 'VALUE' clause is no longer generated for occursed
fields for a BULL-GCOS7 target.
(C:029378)
The 'VALUE' clause is no longer generated for occursed
fields if the 'type of COBOL to generate' is 4 (Bull-Gcos7).

The 'Database code' parameter in the optional
command lines is correctly generated
(C:029383)
The 'Database code' parameter used in the optional command
lines via the Workbench is correctly interpreted in the
generated sources.
In online mode, this parameter corresponds to 'W'.

Elementary Component: Logical View managed
with different types of Persistency Objects.
(C:029403)
The logical access to a Logical View, in a read operation,
was not correct if the main Persistency Object was of
relational or DL1 type
and if there was a secondary Persistency Object
with a different type.
The error has been corrected.

Syntax error in the OnLine Systems Development
generated code (REDFINES)
(C:029481)
Generated code with the BREAKDATE option: there is no
compilation error any more. The REDFINES clause is correctly
generated.

Generation of AD2 operator if 'code for sequence
of generation' is other than the Program code.
(C:029483)
Generation of the AD2 operator when the 'code for sequence
of generation' is different from the Program code.
The AD2 operator is now correctly generated, even if the
'code for sequence of generation' of the Program is
different from the Program code.

The Additional View Description for the standard
SQL functions is correctly generated.
(C:029491)
OnLine Systems Development generated code:
All the sub-functions (F80) which use the SQL declarations
entered in the Segment 'SQL View Description' screen are
correctly generated.

Erroneous generation of CALL for IMS sub-monitors
(CALL '......').
(C:029492)
Generation of IMS submonitor: some CALL were wrongly
generated with CALL '......'. This has been corrected.
It is now generated as CALL 'CBLTDLI' for a 'C'-type
generated language, or CALL 'CEETDLI' for a
'D'-type generated language.

Generation of a Folder with an 'F' type of code
with extract method called in a Macro-Structure.
(C:029514)
Generation of a Folder with an 'F' type of code with
extract method called in a Macro-Structure.

The extract method is generated in the Folder if it is
called by a Macro-Structure and if the call to this
Macro-Structure is specified in two different libraries.

The FST variable in F80-SEGT-P is set to '0'
and then reset to '1' in F80-SEGT-CL
(C:029640)
When an Elementary Component is generated, the
FFNN-FST variable is now set to '0' for an
OPEN curor and to '1' for a CLOSE cursor.

GMS: generation of an Elementary Component:
Transfer of a View data
(C:029866)
GMS: generation of an Elementary Component:
Transfer of a View data

Each data item of a Logical View is now transferred only
once (and no longer as many times as the extraction
parameter of the method is used).
(Function FXXXX-TRVW-CATR: function for the transfer of
data of the XXXX View)

DBD Block, DESCR=ALL option: embedded group Data Elements
are recognized.
(C:029929)
DBD Block, DESCR=ALL option: embedded group Data Elements
are recognized.
With the DESCR=ALL option, the group Data Elements,
constituted of elementary Data Elements, called in DBD
Blocks are recognized.
Now a group Data Element can be constituted of other group
Data Elements.

GCO: correct generation of SQL statements from
description of segment and -GG information
(C:029933)
GCO: For the generation of SQL statements, the line
F80AF 20*C PR42 AD=RN generates the function, sub-function
F80-PR42-AD with the -GG lines of the Segment.

Database Blocks, DESCR=ALL option: recognition of
nested group Data Elements, but not in SQL statements
(C:029976)
The DESCR=ALL option recognizes the group Data Elements,
constituted of elementary Data Elements, in a Database
Block.
Now a group Data Elements can itself be constituted of
other group Data Elements.
Group Data Elements are not generated in SQL statements.

The NUVERS generation option of an Application
Component now contains 5 characters.
(C:030004)
The NUVERS generation option of an Application
Component now contains 5 characters.

DESCR=ALL: Group Data Elements are recognized
for host variables only
(C:030016)
DBD Block, DESCR=ALL: Group Data Elements are recognized,
except in SQL statements and in SQL indicators.
The DESCR=ALL option allows the recognition of group
Data Elements in a DB2 Block, when these groups are
constituted of elementary Elements (Change 27736).
Now a group Data Element can also be constituted of
other group Data Elements. This applies to the Segment
which describes the table but neither to the indicators
(V-ffnn) nor to the SQL statements.

OLSD generation with the MONITOFF option
(C:030053)

OLSD - generation with an IMS variant and a MONITOFF option.
All the procedure lines start in margin B.
(Function F0116).

Erroneous generation of CALL for IMS sub-monitors
(CALL '......').
(C:030065)
Generation of IMS submonitor: some CALL were wrongly
generated with CALL '......'. This has been corrected.
It is now generated as CALL 'CBLTDLI' for a 'C'-type
generated language, or CALL 'CEETDLI' for a
'D'-type generated language.

GCP: Segment with an initial value
(C:030067)

GCP: Segment with an initial value

The Programs which contain Segments with initial values are
correctly generated.

GCO: level of a date-type Data Element which
is part of a group
(C:030127)
GCO: Now the levels of date-type Data Elements are
correct, even if these Data Elements belong to a group.

GCO: Standard accesses were not generated in
F80-ffnn-R if an F80 function overrode an access
(C:030141)
GCO: Now the SQL standard accesses are generated even
if an F80 function overrides one of the standard accesses.

Errors in the generation of a Program in
'Cobol Source' (-9)
(C:030149)
Errors in the generation of a Program in
'Cobol Source' (-9)

1) Generation of a Programme (P) in 'Cobol Source' (-9)
with the option for the suppression of Cobol numbering.
With the Change 27735 (breakdown of dates), extraneous lines
may wrongly appear in a Program written in lines 9 with the
'suppression of Cobol numbering' option.
This has been corrected.

2) Generation of a Program (P) in 'Cobol Source' (-9)
with a '/' in column 7
This '/' line is replaced, in the generated code, with
extraneous lines.
This has been corrected: the '/' line remains as is in
the generated code.

Data Element with a TimeStamp type (TS) was
wrongly generated with a length of 8 instead of 26
(C:030170)
A Data Element with a TS type (Timestamp) was wrongly
generated with a length of 8 instead of 26.
This has been corrected.

The replacement of functions via the *R condition
type was not correct.
(C:030192)
The replacement of functions via the *R condition
type was not correct if the replacement sub-function
was alphabetically before the file code.
This has been corrected.

Generation

GPRT: Possibility to specify the Application code
of SCM on the FLx flow cards or -GO of Library
(C:021444)
GPRT: Possibility to specify the Application code of SCM on
FLx flow cards or on the -GO lines of the Library.
The user can specify in the -GO lines of the Library, in
addition to the Default or Required Environment code by
entity type, the corresponding Application code. The
line is as follows:
Col. 1...+...10....+...20....+...30....+...40
EEE DE RE DADADADADA RARARARARA
where EEE : entity type,
DE : Default Environment short code,
RE : Required Environment short code,
DADADADADA : Default Application code,
RARARARARA : Required Application code.

And, at generation, the user can specify on the Flow cards,
in addition to the Environment short code, the Application
code of this Environment.

This latter is coded as one of the Flow cards options, i.e.
as follows:
APPLI=xxxxxxxxxx where 'xxxxxxxxxx' is the Applicati
code value, on 10 characters maximum.

The APPLI option is taken into account in the follow
cases:
- presence of the Default/Required Environment code in the
-GO lines of the Library, without corresponding Application
code and absence of the Environment short code on the Flow
cards,
- absence of the Required environment code in the -GO lines
of the Library and presence of the Environment short code
on the Flow cards.

Controls are performed and if the Application specified
at APPLI option level does not exist in the selected
Environment, the Application to which one is linked the
generated entity is taken into account. Otherwise, the
'**********' Application is taken into account.

The presence of a new Flow card overrides the codification
of the options of all the previous Flow cards in the same
generation requests flow.

GPRT submission via GP screen
(C:027904)

When submitting jobs via the GP screen, all the user's
generation requests are taken into account, whatever the
library, but in the connection session only.

Generation of COPY clause in batch: the CCF/CCB
on the first * line are not correctly processed
(C:028392)
Generation of COPY clause in batch: the before/after cards
on the first * line were not correctly processed.
This has been corrected.

Generation of Programs: the job cards parameters
are not correctly set from the 10th...
(C:028395)
Generation of Programs in batch: the job cards parameters
are not correctly set if there are 10 or more parameters.
The parameters were not correctly set from the 10th
parameter, and this for all job cards.
This has been corrected.

You can set the cursor on an entity code in the
GP screen.
(C:028869)
You can set the cursor directly on a line in the
GP screen.
Structure of the command:
GP and then the GPRT command on 4 positions and then the
entity code.
Blanks between the command and the entity must be filled in
with '&'.
Example: GP GCP&PGMXXX

Error 1743E - GENERATION REFUSED: MAXIMUM NUMBER
OF RIGHTS IS REACHED for a permanent right
(C:029082)
The error 1743E - GENERATION REFUSED: MAXIMUM NUMBER OF
RIGHTS IS REACHED was erroneously generated for a user
having a permanent right, when the maximum number of
connections of users without permanent right was reached.
Corrected.

Variants control: the search for
entities to be generated is made in C1 view.
(C:029236)
Generation request:
All generation requests are made in 'C1' view, as
for the control of generation licenses.

Generation-print request: deletion of a line
(C:029273)

GP screen: the management of the creation of a line with
opening of a continuation line (continuation area filled in)
is processed independently of the action done on the
previous line.

The GEO command only recognizes the lines which
are filled in and different from '_' (underscore).
(C:029603)
The GEO command only recognizes the lines which
are filled in and which are different from '_' (underscore).
The continuation lines which contain '__' are ignored.

GP screen: Format of the job name displayed when
the job is submitted (Unix and Windows)
(C:029616)
The job name is built from a particular line found in the
GP screen (C4 option) or in the 'Generation scripts' tab
of the generation manager for Developer workbench.
For Windows, this line, which must be the first displayed,
is formatted as 'job id=xxxxxxxx'.
For Unix, this line will be the first line formatted as
'# xxxxxxxx'.
In both cases, the job name will be 'xxxxxxxx', with
eight characters maximum.

GP screen: Refresh of the screen after the
submission of a job.
(C:029649)
GP screen: After a job is submitted, the screen is
correctly refreshed.

BVPGP: the generation script is formatted according to
the Unix standard (Unix repository)
(C:029658)
The line which indicates the shell type (ex: #/usr/bin) at
the beginning of the script is always the first line of
the generation script, even if lines are added in the
generation process.

The writing of the job number is protected
if it has already been created
(C:029729)
The job number specific record is written in the LB file
(job monitoring) only if it has not already been processed
by the GP screen when the GPRT was submited in on-line mode.

PG25: The language code is retrieved for the
GED, GEO and GEC commands
(C:029846)
PG25: The language code is retrieved for the
GED, GEO and GEC commands
When the PG file was retrieved, the language code was not
recognized for the GED, GEO and GEC command lines.
This used to cause an incoherent display of these lines on
the GP screen.
This has been corrected.

GP screen: A same command existing in 2 different
libraries is correctly taken into account
(C:029868)
GP screen: A same command existing in 2 different libraries
and the FLO and FLP commands are correctly taken into
account.

GP screen: resources are freed if an error
occurs upon the sumbission of a job
(C:030180)
GP screen: resources are freed if an error
occurs upon the sumbission of a job
Submitting a generation-print job if the GP screen (C4
option) was empty used to block the Administration database.
This has been corrected.

Database management

The transactions on non-children data elements
generated by CPSN for the update were not correct
(C:028218)
The transactions on non-children data elements
generated by CPSN for the update were not correct.
The code of the parent data element was generated with '&'
for a possible setting to blanks but these '&' character
were not correctly processed but the update.
Corrected.

Incrementation of the current session if an update
straddles two days
(C:028714)
When the batch update procedures UPDT and UPDP were executed
by night, if the update step began before midnight and
finished after midnight, the current session number was
abnormally incremented.
This has been corrected.

REST procedure: the problems of update at
transactions recovering are solved
(C:028924)
At restoration with archived transactions recovering, the
transactions concerning virtual libraries are correctly
processed.

MLIB: The Database is no longer open when a network
initialization is requested.
(C:028982)
When a network initialization is requested, it is not
necessary to take the existing libraries into account.
The Database files will then no longer be open.

Journalization of eBusiness entities deletion
transactions (requested from D. workbench)
(C:029142)
The deletion transaction of a folder entity with deletion
if its depending elements in lower level libraries is
correctly journalized.
The restoration with retrieval of archived transactions
takes this transaction into account.

UPDT continuation of GBIR: Input Aid calls
(C:029164)

In case of an Input Aid call in the same transactions
flow, some transactions depending on this call could
be erroneously rejected.
The error has been corrected.

Update of the data output by the UTM1 and UTM2
procedures.
(C:029508)
Updating the data output by the UTM1 and UTM2
procedures in all sessions, even the old current sessions
of the database, must be allowed.
The update is possible only in a T or H session or in the
current session.
The old current sessions are transformed into the next
greater H session to allow for the update in all cases,
even if the Definition of the Library in which the update
will be carried out was modified in a session greater than
that of the processed record.

The error message 'data file not available'
no longer entails access to the file (ARAD).
(C:029653)
Administration Database archiving: the error message
indicating that the data file of the Administration Database
is not available, no longer entails access to the file.

A restoration with the retrieval of archived
transactions runs correctly.
(C:029752)
REST procedure:
The archived transactions are retrieved correctly ; the
update authorizations are not lost.
The message 2586E does no longer appear in the execution
report.

A rest. with the retrieval of archived tranactions
correctly processes the fields reset to blank.
(C:029788)
When a field is reset to blank by a batch update
transaction, the database restoration with the retrieval
of such a transaction runs correctly.

REOR: The internal table of assigned indexes
is correctly reinitialized.
(C:029949)
In the reorganization procedure, a processing consists in
storing all the images of an assigned index according to
the various sessions.
When this 1000-item table is full, it is emptied and
correctly reinitialized. This will prevent the duplication
in the writing of indexes (abend in REST).

Graph

The 'image' entities are controlled only
at creation.
(C:030114)
Now the image entities are controlled only when they do not
already exist.

On line help

HS and HO sub-menus: -Gx for the documentation,
help, generation and options
(C:029643)
In the HS and HO sub-menus, the -Gx line is now
titled 'documentaion, help, generation and options' because
'Gx' is sub-divided into GC, GE, GG, GO.

LEG choice: the on-line help is now available
(C:029960)

LEG choice: the on-line help is now available

MERISE methodology

PDM : the -XQG choice is now possible and not
rejected for all the entities
(C:030063)
PDM : the -XQG choice is now possible and not
rejected for all the entities

Meta-entities

PAF: Extraction on /YTTDEF with a WHERE clause
on UEOC and another condition
(C:028119)
The extraction conditioned by a WHERE clause with
UEOC = variable and a condition on another column having
an 'alphanumeric value' type is now correctly executed.

An extraction on TTXCRLCAL with some conditions
(entity code + relation) was erroneous.
(C:029478)
An extraction on TTXCRLCAL with a particular
condition on the entity code CUEO with a cobol
variable and with an alphanumeric value on the
relation code is now correct.

With the 'From...' choice on a Meta-Entity U.E.
list, conversion into uppercase (FxxxL , 1xxxLY)
(C:029622)
With the 'From...' choice on a Meta-Entity U.E.
list, conversion into uppercase (FxxxL , 1xxxLY)

If the 'uppercase' option (related to the U.E. code)
has been specified on a Meta Entity, the characters entered
after L or LY to view the list from a code are conve
into upper case letters.

For the 'old' Meta-Entities, the PAF extractor now
recognizes the real length of the Data Element
(C:030145)
For the 'old' Meta-Entities, the PAF extractor now
recognizes the real length of the Data Element
This change applies to the /YTTDEF and
/YTTDxx tables (xx = description number).

Metamodel

The methodology entities can also be
accessed with a Developer Workbench right
(C:028736)
The methodology entities (Merise, OMT...) can be accessed
via Pacbench only with a Developer workbench use right.
This access does not require the optional 'Extensibility'
module.

On-Line System Development

SQL non standard access: if group data element in
a segment, preceding data element sent twice
(C:028759)
SQL non standard access: if an SQL table contains a group
data element, the data element which precedes this group
data element is sent twice. If it is the first data element
of the segment and if there is another segment before, the
last data element of the preceding segment is also sent.
Corrected.

In the SQL orders, the format of data elements
having an extended date format is no more truncate
(C:029068)
In the SQL orders, the format of data elements
having an extended date format is no more truncated.
In the generated F80 functions, some lines associated with
data elements having an extended date format specified on
their 'element description' screen might be truncated.
This has been corrected.

Initialization of the CENTUR area to 20
(C:029149)

For the generation of dialog program, C/S component or
eBusiness component, the CENTUR area is now initialized
to '20' instead of '19'.

NonStop SQL: generation of SQL orders for
DATE-type data elements
(C:029160)
NonStop SQL: the generation of SQL orders for DATE-type
data elements was not correct.
'àTYPE AS ...' was generated instead of 'TYPE AS ...'.
This has been corrected.

Generation of screen with PCB call: erroneous
error message
(C:029178)
Generation of screen with DL1 database: the control of
the database is correctly performed.

GCO - The initial value is now recognized for a
Data Element displayed and protected on the screen
(C:029304)
GCO - The initial value is now recognized for a
Data Element displayed and protected on the screen

In a Screen description (-CE with a C2 option), if you enter
an initial value for a displayed and protected Data Element
(nature 'F'), the loading of the initial value is generated
in the 'O-' in F8115.
!!! The BMS bitmap is not changed !!!

The 'VALUE' clause is no longer generated for occursed
fields for a BULL-GCOS7 target.
(C:029378)
The 'VALUE' clause is no longer generated for occursed
fields if the 'type of COBOL to generate' is 4 (Bull-Gcos7).

Syntax error in the OnLine Systems Development
generated code (REDFINES)
(C:029481)
Generated code with the BREAKDATE option: there is no
compilation error any more. The REDFINES clause is correctly
generated.

The Additional View Description for the standard
SQL functions is correctly generated.
(C:029491)
OnLine Systems Development generated code:
All the sub-functions (F80) which use the SQL declarations
entered in the Segment 'SQL View Description' screen are
correctly generated.

Erroneous generation of CALL for IMS sub-monitors
(CALL '......').
(C:029492)
Generation of IMS submonitor: some CALL were wrongly
generated with CALL '......'. This has been corrected.
It is now generated as CALL 'CBLTDLI' for a 'C'-type
generated language, or CALL 'CEETDLI' for a
'D'-type generated language.

Generation of SELECT without the FROM clause
when this clause is on the left of the -GG
(C:029768)
OnLine Systems Development: the FROM clause is recognized
in the SELECT generation, even if it is located on the
left of the Segment -GG screen.
This generation is identical to the batch generation.

DBD Block, DESCR=ALL option: embedded group Data Elements
are recognized.
(C:029929)
DBD Block, DESCR=ALL option: embedded group Data Elements
are recognized.
With the DESCR=ALL option, the group Data Elements,
constituted of elementary Data Elements, called in DBD
Blocks are recognized.
Now a group Data Element can be constituted of other group
Data Elements.

GCO: correct generation of SQL statements from
description of segment and -GG information
(C:029933)
GCO: For the generation of SQL statements, the line
F80AF 20*C PR42 AD=RN generates the function, sub-function
F80-PR42-AD with the -GG lines of the Segment.

Database Blocks, DESCR=ALL option: recognition of
nested group Data Elements, but not in SQL statements
(C:029976)
The DESCR=ALL option recognizes the group Data Elements,
constituted of elementary Data Elements, in a Database
Block.
Now a group Data Elements can itself be constituted of
other group Data Elements.
Group Data Elements are not generated in SQL statements.

DESCR=ALL: Group Data Elements are recognized
for host variables only
(C:030016)
DBD Block, DESCR=ALL: Group Data Elements are recognized,
except in SQL statements and in SQL indicators.
The DESCR=ALL option allows the recognition of group
Data Elements in a DB2 Block, when these groups are
constituted of elementary Elements (Change 27736).
Now a group Data Element can also be constituted of
other group Data Elements. This applies to the Segment
which describes the table but neither to the indicators
(V-ffnn) nor to the SQL statements.

OLSD generation with the MONITOFF option
(C:030053)

OLSD - generation with an IMS variant and a MONITOFF option.
All the procedure lines start in margin B.
(Function F0116).

GCO: level of a date-type Data Element which
is part of a group
(C:030127)
GCO: Now the levels of date-type Data Elements are
correct, even if these Data Elements belong to a group.

GCO: Standard accesses were not generated in
F80-ffnn-R if an F80 function overrode an access
(C:030141)
GCO: Now the SQL standard accesses are generated even
if an F80 function overrides one of the standard accesses.

Data Element with a TimeStamp type (TS) was
wrongly generated with a length of 8 instead of 26
(C:030170)
A Data Element with a TS type (Timestamp) was wrongly
generated with a length of 8 instead of 26.
This has been corrected.

The replacement of functions via the *R condition
type was not correct.
(C:030192)
The replacement of functions via the *R condition
type was not correct if the replacement sub-function
was alphabetically before the file code.
This has been corrected.

Va Pacbase/DSMS Interface

Freezing of a Database under DSMS control
via batch procedures
(C:029288)
A Database freezing request via the update batch
procedures is not monitored by DSMS, like in
Developer workbench.

The entity type will be correctly tested on
-CR screens.
(C:029654)
DSMS control in VA Pacbase:
Controls will be correctly performed on -CR screens.

Pacbase Access Facility

PAF/Table YTTAPE : the code of the chained entity
was truncated to 7 characters.
(C:028112)
After an extraction on the PAF table /YTTAPE, the co
the chained entity which should be 30 characters long is
truncated to 7 char. This is now corrected.

PAF: Extraction on /YTTDEF with a WHERE clause
on UEOC and another condition
(C:028119)
The extraction conditioned by a WHERE clause with
UEOC = variable and a condition on another column having
an 'alphanumeric value' type is now correctly executed.

PAF: The maximum number of data elements to be
extracted for a table was limited to 20
(C:028324)
If an entity description contains more than 20 data
element, the PAF extractor correctly extracts all the data
elements.
This concerns all the extractions on all the PAF tables.

Extractor by keywords (PAFBWS): correction of
file access errors
(C:028489)
The batch extractor for searches by keywords (PAFBWS) has
been corrected to avoid file access errors.

SEGDEL: 'I' view with a selection on a Data
Element called in a lower-level library
(C:028696)
PAF /SEGDEL: Importing with an 'I' view now works fine if
there is a selection on a Data Element called in a
lower-level library.

PAF/LOCKS: The access to the locks PAF table
was not correct for the segment-type entities
(C:028698)
The access to the locks PAF table was not correct for the
segment-type entities.
The extractor now correctly sends back the lock origin
(technical or user).

PAF: The OPEN orders on all tables send back
FI='1' if there is a condition on a numeric column
(C:028757)
PAF: The OPEN orders on all tables send back FI='1' if there
is a condition on a column which format is numeric
(1 character gap in the key of the read index).

PAF /YTTDEF: it is possible to make a selection
on a Data Element linked with a User Entity.
(C:028806)
PAF /YTTDEF: it is now possible to make a selection
on a Data Element linked with a User Entity.

The extraction of /YTTDEF with linked entities
generated the repetition of some fields
(C:028846)
The result of a PAF request on the definition of user entity
was erroneous in some cases:
- the description of the meta entity, for this definition
(-CE00), contained data elements linked to other user
entities.
- some of the fields corresponding to these data elements
were not filled in on the user entity definition.
PAF repeated the value of the filled in fields in those
empty fields.
This has been corrected.

PAF: If a program only calls the extractor for
keywords: error on the SYSPAF file
(C:028885)
PAF: if a program only calls the extractor for keywords
(BVPBBTWS): error when writing the SYSPAF file.
Corrected.

The access to the locks table with the user code
returned a 'D' type instead of 'S'
(C:028886)
The access to the locks table with the user code returned
a 'D' type instead of 'S'.
This is now corrected.

PAF, LCKENT table: addition of lock type
(technical or user)
(C:028887)
LCKENT table: addition of lock type (technical or user) -
TVER/TLCK.
This field is space, in case of user lock, or 'Y' in case
of technical lock (download Pacdesign).

PAF: The extraction on the LOCKS table must output
'PGM'-coded entities
(C:028979)
PAF: The extraction on the LOCKS table must output 'PGM'-,
'SCR'-, ...-coded entities and not 'P'-, 'O'-, ...-coded.

PAF: Optimized controls of the elementary
conditions for User Entities
(C:029198)
PAF: Optimized controls of the elementary
conditions for User Entities
Some access controls (among which the control on meta-entity
descriptions) were performed several times by entity,
which is useless and costly.
These accesses have been optimized.

PAF: The extraction of user entity description
with a condition on entity code is possible
(C:029232)
PAF: The extraction of user entity description with a
condition on entity code is possible.

A PAF extractor retrieves all the data included
in the requested description
(C:029312)
PAF extractor on User Entities
All the data of the requested description is retrieved
by the extractor, whichever the length of the
description is.

PAF: The /YTTXRL... tables with a condition on
the user entity code are correctly extracted
(C:029375)
PAF: The /YTTXRL... tables with a condition on the u
entity code are correctly extracted.
FI = '1' is no more generated at first read (what was due to
a shift in the linkage on the index areas).

An extraction on TTXCRLCAL with some conditions
(entity code + relation) was erroneous.
(C:029478)
An extraction on TTXCRLCAL with a particular
condition on the entity code CUEO with a cobol
variable and with an alphanumeric value on the
relation code is now correct.

Extraction on /YTTDEF tables with 2 conditions
joined with 'OR' on the user entity is correct
(C:029518)
Now a definition table can be extracted for a user entity
with a clause which contains the following selection:
WHERE COEU = 'value 1'
OR COEU = 'value 2'
This error also impacted the other VA Pac entities.

The value of the SIZE parameter mustn't limit the
extractions on the /YTTDEF PAF tables.
(C:029572)
The value of the SIZE parameter mustn't limit the number of
extractions on the /YTTDEF PAF tables.
All the other entities are also concerned by this
change.

The return code of CONNECT on the WORDSEARCH Table
in the keyworkds TP extractor is correct.
(C:029584)
The return code of CONNECT on the WORDSEARCH Table
in the keyworkds TP extractor is correct.

Online PAF: correction of online PAF extractions
(standard extractor + keywords extractor)
(C:029609)
Online PAF: correction of online PAF extractions
(standard extractor + keywords extractor)

Extraction on description of database block :
return of the key data elements
(C:029712)
Information about the description of relational database
block (with more than 8 key data elements on the -K) were
returned into 2 rows instead of one : this is now corrected.

The extraction of User Entities retrieved from
V2.5 now also retrieves all their keywords
(C:030057)
The extraction of User Entities retrieved from
V2.5 now also retrieves all their keywords.

/YTTDxx : Extractions of user entity's
descriptions are now correct (follow-up C30057)
(C:030090)
/YTTDxx : Extractions of user entity's
descriptions are now correct (follow-up C30057)

For the 'old' Meta-Entities, the PAF extractor now
recognizes the real length of the Data Element
(C:030145)
For the 'old' Meta-Entities, the PAF extractor now
recognizes the real length of the Data Element
This change applies to the /YTTDEF and
/YTTDxx tables (xx = description number).

Personalized Document. Manager

PDM : the -XQG choice is now possible and not
rejected for all the entities
(C:030063)
PDM : the -XQG choice is now possible and not
rejected for all the entities

Pacbench Quality Control

PQC: if there was several * cards, the library
of the PACQIG report was erroneous
(C:027810)
PQC: if there was several * cards, the library
of the PACQIG report was erroneous.
Corrected.

PQC: The rule related to the absence of Text
assigned to a Program was wrongly indicated.
(C:028554)
PQC: The rule related to the absence of Text assigned to
a Program was wrongly indicated.
This has been corrected.
However, assigned Texts are recognized only if the PQC
request is made with the C2 option.

PQC: A condition on the keywords of a definition
is operational
(C:029238)
PQC: A condition on the keywords of a definition is
operational.

Batch Procedures

REOR procedure: purge of programs, dialogues and
eBusiness entities
(C:027976)
A program purge request deletes the calls in the entities
of the eBusiness model, the programs and the screens.

The transactions on non-children data elements
generated by CPSN for the update were not correct
(C:028218)
The transactions on non-children data elements
generated by CPSN for the update were not correct.
The code of the parent data element was generated with '&'
for a possible setting to blanks but these '&' character
were not correctly processed but the update.
Corrected.

Restoration with 'REC' option: return code
no more sent back for warnings
(C:028221)
In case of restoration with the 'REC' option, the return
code is no more sent back for the warnings.
The transactions cause of these warnings were not
printed. The return code, set to 2, to alert the user
does not have any interest.

PUPM: Purge procedure with save of the last
generation trace for BASIC environments
(C:028248)
For BASIC environments, a purge procedure keeps only the
trace of the last generation of the entity, in all
production sessions (ex-PEI functions).
The transactions output of the generation must first be
transferred into the repository.

CPSN and EXPJ : the identification line for PIA
calls was missing in some cases.
(C:028307)
GBIR-CPSN and EXPJ : the identification line for PIA calls
was missing in some cases. When the content of a called PIA
was modified selsewhere than on the first description line,
the update of this new content was erroneous because of
the identification line absence. This line is required for
extractions to format the file before the update, but it
must not appear in case of modification during the update.
This is now corrected.

EXLI: erroneous extraction of the deleted
children data elements
(C:028418)
The deleted children data elements were erroneously
extracted.
This has been corrected.

In an erroneous context, the rejected transactions
management and printing may be incorrect
(C:028501)
In case of erroneous context, the management and printing of
the rejected transactions may be incorrect.
According to the context, rejected lines might have been
printed several times and the transactions file did not
contain all the rejected transactions.
This is now corrected.

Lowercase characters are wrongly converted in the
documentation transactions for input aid calls
(C:028569)
Lowercase characters are wrongly converted into uppercase
in the documentation transactions after input aid calls.
This has been corrected.

GBIR: take into account the change number
specified on the input card of CPSN
(C:028725)
GBIR: take into account the change number specified on the
input card of CPSN.
Corrected.

No more conflicts on the AJ file.
(C:028769)

The GPRT procedure has been modified in order to prevent
conflicts on the AJ file between the archiving procedure
and the generation procedure.

GPRT: The return codes are now correctly
transmitted to the procedure
(C:028880)
As a result of the modification of the physical accesses
management, some return codes were not correctly transmitted
to the procedure.
This has been corrected.

REST: File codes are indicated if an error occurs
(AN-AR-AY).
(C:028881)
If an error occurs in the Database files upon the
restoration phase (PTU400), the following file codes are
retrieved: AN for indexes, AR for data and AY for long data.

PC25: all the 2.n technical locks must be
ignored
(C:028909)
PC25: the 2.n technical locks are no more transferred.

SCM entities controls in the batch procedures
(C:028913)

The checks performed in the batch procedures on the
SCM transactions are removed as the transactions
are considered as correct because they are extracted
from Developer workbench.
This concerns the UPDT, UPDP and REST (REC option)
procedures.

REST procedure: the problems of update at
transactions recovering are solved
(C:028924)
At restoration with archived transactions recovering, the
transactions concerning virtual libraries are correctly
processed.

The return code 16 (capacity overflow of sort files)
was not correctly managed in the STAT procedure.
(C:028939)
Now, the return code 16 (capacity overflow of sort files)
is correctly managed in the STAT procedure.

MLIB: The Database is no longer open when a network
initialization is requested.
(C:028982)
When a network initialization is requested, it is not
necessary to take the existing libraries into account.
The Database files will then no longer be open.

PG25 defects and download of components linked
to the repository on ACUCOBOL.
(C:028986)
The transactions output of PG25 are no more rejected by the
retrieval.
The download of descriptions of a non existing business
component does no more generate a abnormal ending.
Those defects are linked to the ACUCOBOL compiler: the
technical area must be initialized and differently used
in the programs.

CPSN: table boundary violation in user entities
management
(C:029049)
CPSN: table boundary violation in user entities management.
A table containing all the extension user entities of the
master database was filled in by all the user entities
(client and extension).
A number of U.E. higher than 1000 generated a table
boundary violation.
This table must be changed at VINS procedure execution and
not with a standard CPSN.

Screen entities taken into account in
the EXPU extraction procedure.
(C:029114)
Now, the Screen entity instances ('O') are processed
in the Extraction for Purge procedure (PACX - EXPU).

In the batch update, an error on a transaction
could also affect the following transactions.
(C:029128)
In the batch update, an error on a transaction could also
affect the following transactions.
If consecutive transactions were related to the same
description of a User Entity, an error detected on a
transaction wrongly affected the next transactions with
the error message 'ERROR MESSAGE NOT FOUND'.
This has been corrected.

UPDT continuation of GBIR: Input Aid calls
(C:029164)

In case of an Input Aid call in the same transactions
flow, some transactions depending on this call could
be erroneously rejected.
The error has been corrected.

GBIR: Initialization of fields useless for
subnetworks comparison.
(C:029185)
When comparing subnetworks, Program entities were
generated due to an error.
Some fields of the data are now correctly initialized and
these programs are no longer generated.

CPSN: when a text was deleted, the sort of
transactions was not correct.
(C:029221)
Now, the transactions for text deletion are sorted
by CPSN procedure as follows:
- deletion of text descriptions,
- deletion of the description 'L' line, corresponding to
the division title,
- deletion of the definition screen.
The definition is deleted lastly.

CPSN: management of implicit and explicit
action codes
(C:029224)
CPSN: management of implicit and explicit action code.
The implicit update of description of screen (-CE) generated
the creation of 000 lines.
Corrected.

Until now, when a CPSN was executed:
-in case of explicit update (option 2, position 33 or 34
of the CPSN card), the '&' characters were considered as
blanks (C or M actoin code)
- in case of implicit update (option 1, position 33 or 34
of the CPSN card that generates an X action code), the
'&' characters were considered as significative characte
Novelty:
For an explicit update, take into account the significative
'&' (for example in the data element label) and distingu
them from the '&' used as blanks (example: in the 'pare
element' field of a non child data element).
This has been corrected.

Variants control: the search for
entities to be generated is made in C1 view.
(C:029236)
Generation request:
All generation requests are made in 'C1' view, as
for the control of generation licenses.

CPSN: process the deletions before the creations
for some cases of input aid call
(C:029247)
CPSN: process the deletions before the creations for some
cases of input aid call
If an entity calls two different input aids in two networks
or if in one network the -G is an input aid call and in the
other network, a comment line, the deletion of the slave
network transaction must be generated before the creation
of the master network transaction.
Corrected.

CPSN: incomplete data elements keywords
formatting
(C:029262)
CPSN: incomplete data elements keywords formatting.
The keywords of data elements are not processed if the
data elements definitions are the same in the master and
in the slave files.

Freezing of a Database under DSMS control
via batch procedures
(C:029288)
A Database freezing request via the update batch
procedures is not monitored by DSMS, like in
Developer workbench.

HIPM procedure: management of SCM records
(C:029314)

Upon PEI retrieval, environments were created with a
'BASIC-type configuration' and a 'basic'-type management.
As a consequence, as for PEI, only the latest production
turnover session of an instance is kept.
Globally, the production turnover information is
saved in the session frozen via the HIPM procedure.
With a 'basic'-type management, all the records which
correspond to a previous production turnover are deleted.
In the opposite case, all this data is kept, so a historical
account of production turnovers is made possible.

Be careful: the HIPM procedure must be re-installed
as the length of the SR and TR files has changed.

The UTM1 and UTM2 procedures no longer go into an endless
loop.
(C:029404)
The UTM1 and UTM2 procedures no longer go into an endless
loop. These procedures now work fine.

Amélioration de la procédure UKD1
(C:029443)

Additional control:
Assigning rights to a group of users ('U' line) and
activating a new key ('K' line) cannot be done in the same
flow.

Warning: assigning a key is possible only if the perimeter
of this new key is identical to that of the old key.

Update of the data output by the UTM1 and UTM2
procedures.
(C:029508)
Updating the data output by the UTM1 and UTM2
procedures in all sessions, even the old current sessions
of the database, must be allowed.
The update is possible only in a T or H session or in the
current session.
The old current sessions are transformed into the next
greater H session to allow for the update in all cases,
even if the Definition of the Library in which the update
will be carried out was modified in a session greater than
that of the processed record.

Processing of comment lines in the batch update.
(C:029534)

UPDP-UPDT: Processing of comment lines in the batch update.
If the line number was not indicated, only the last
transaction was recognized.

The End of File was not correctly managed when
/dev/null was used (Unix repository)
(C:029610)
UTM2 Procedure:
The end of processing is now correctly managed in the update
step if a 'DUMMY' file (/dev/null) is used.

PACX-EXTR: The extracted data element keywords
are no more duplicated
(C:029648)
PACX-EXTR: The extracted data element keywords are not
duplicated anymore.
The keywords of data element were processed twice when an
extraction with update by UPDT ware requested.
Corrected.

The error message 'data file not available'
no longer entails access to the file (ARAD).
(C:029653)
Administration Database archiving: the error message
indicating that the data file of the Administration Database
is not available, no longer entails access to the file.

A restoration with the retrieval of archived
transactions runs correctly.
(C:029752)
REST procedure:
The archived transactions are retrieved correctly ; the
update authorizations are not lost.
The message 2586E does no longer appear in the execution
report.

A rest. with the retrieval of archived tranactions
correctly processes the fields reset to blank.
(C:029788)
When a field is reset to blank by a batch update
transaction, the database restoration with the retrieval
of such a transaction runs correctly.

Management of the return code sent by the procedures
which require the TP server to be inactive (Unix repository)
(C:029903)
Management of the return code sent by the procedures
which require the TP server to be inactive (Unix repository)
The ARCH, PACS, PE25, PG20, PG25, REST and VINS
procedures, whose execution requires the TP server to be
inactive, will end with a return code 12 if the server is
active.

CPSN: management of the input and output formats
of Data Elements
(C:029942)
CPSN: management of the input and output formats
of Data Elements
When the three formats of a Data Element are identical in
a master network but different in a slave network, the
input and output formats of the master Data Element must
become the new formats of the slave Data Element.
Corrected.

REOR: The internal table of assigned indexes
is correctly reinitialized.
(C:029949)
In the reorganization procedure, a processing consists in
storing all the images of an assigned index according to
the various sessions.
When this 1000-item table is full, it is emptied and
correctly reinitialized. This will prevent the duplication
in the writing of indexes (abend in REST).

CPSN: If formatting request for UPDT, correct
processing of continuation lines if large volumes.
(C:029973)
CPSN: if a formatting was requested for UPDT, the MV file
became incoherent when records including continuation lines
were processed.
The incoherence occurred right after the processing of a
very large amount of records.
This problem upon the writing of the MV file is now
corrected.

Reconstitution of the x-references for User
Entities
(C:030032)
If the description of a Meta Entity has been moved to a
higher-level library (deletion and then creation in the
same session number), the indexes of the corresponding
User Entities are correctly reconstituted by the
reorganization procedure (REOR).
A reorganization must then be run to make this correction
effective.

Retrieve

Harmonization of the default codes (Environment,
Application) of the retrieval and the generation
(C:028331)
Harmonization of the default codes (Environment,
Application) of the retrieval and of the generation.
The procedure used to retrieve PEI data initializes the
default environments and applications with '*' characters
as it is done in the generation.
The BVPPP25 procedure retrieves the 2.5 PP file of PEI to
update the VA Pac development database.

PC25: case of a same manual (U) created in
several libraries
(C:028344)
PC25: The case of a same manual (U entity) created in
several libraries was not correctly processed.
All the libraries must be taken into account.
This is corrected.

PC25: Do not take into account the action code of
user entities contituation transactions
(C:028652)
PC25: Do not take into account the action code of the user
entities continuation transactions.
When in 2.n version, the continuation transaction only was
deleted, the retrieval created a new transaction (which
groups all the 2.n transactions of a U.E.O.) and this
transaction was wrongly deleted.
The action code of the first transaction only must be taken
into account.

PC25: all the 2.n technical locks must be
ignored
(C:028909)
PC25: the 2.n technical locks are no more transferred.

In the batch update, an error on a transaction
could also affect the following transactions.
(C:029128)
In the batch update, an error on a transaction could also
affect the following transactions.
If consecutive transactions were related to the same
description of a User Entity, an error detected on a
transaction wrongly affected the next transactions with
the error message 'ERROR MESSAGE NOT FOUND'.
This has been corrected.

PJ25: In the keywords retrieval, the '&' character
must be considered as a blank
(C:029130)
PJ25: In the keywords retrieval, the '&' character must
considered as a blank.
When '&&' is present in the U.E call code area on th
keyword transaction, the keywords were erroneously
considered as linked to a user entity.
Corrected.

PE25: a user becomes administrator when its
authorization level for PARM was 4 in 2.5
(C:029372)
PE25: a user becomes administrator when its authorization
level for PARM was 4 in 2.5.

PP25: if there is a request for update in session 1, a list
of the managed entities is loaded by default
(C:029485)
PP25: if the user requests the update of the environements
in session 1 and in inter-library mode, a list of the
managed entities is loaded by default.
Programs, Dialogs, DBS and copy will be managed by
these environments.
Upon the retrieval, the environement management tool is
loaded with 'BASIC'.

PC25: The type to be given to the Input Aid call line
must not come from a comment line.
(C:029743)
PC25: The type to be given to the Input Aid call line
must not come from a comment line.
The type present on the Input Aid description (except
comment lines) determines the value of the Input Aid type
in the Definition, i.e. 'C' for Comments, 'G' for Generation
Elements or 'O' for Generation Options.
So Input Aid calls may be displayed in -GC, -GG or -GO
screens.

PG25: The language code is retrieved for the
GED, GEO and GEC commands
(C:029846)
PG25: The language code is retrieved for the
GED, GEO and GEC commands
When the PG file was retrieved, the language code was not
recognized for the GED, GEO and GEC command lines.
This used to cause an incoherent display of these lines on
the GP screen.
This has been corrected.

Software Config. Management

GPRT: Possibility to specify the Application code
of SCM on the FLx flow cards or -GO of Library
(C:021444)
GPRT: Possibility to specify the Application code of SCM on
FLx flow cards or on the -GO lines of the Library.
The user can specify in the -GO lines of the Library, in
addition to the Default or Required Environment code by
entity type, the corresponding Application code. The
line is as follows:
Col. 1...+...10....+...20....+...30....+...40
EEE DE RE DADADADADA RARARARARA
where EEE : entity type,
DE : Default Environment short code,
RE : Required Environment short code,
DADADADADA : Default Application code,
RARARARARA : Required Application code.

And, at generation, the user can specify on the Flow cards,
in addition to the Environment short code, the Application
code of this Environment.

This latter is coded as one of the Flow cards options, i.e.
as follows:
APPLI=xxxxxxxxxx where 'xxxxxxxxxx' is the Applicati
code value, on 10 characters maximum.

The APPLI option is taken into account in the follow
cases:
- presence of the Default/Required Environment code in the
-GO lines of the Library, without corresponding Application
code and absence of the Environment short code on the Flow
cards,
- absence of the Required environment code in the -GO lines
of the Library and presence of the Environment short code
on the Flow cards.

Controls are performed and if the Application specified
at APPLI option level does not exist in the selected
Environment, the Application to which one is linked the
generated entity is taken into account. Otherwise, the
'**********' Application is taken into account.

The presence of a new Flow card overrides the codification
of the options of all the previous Flow cards in the same
generation requests flow.

SCM: Online screen to visualize generation
information (ex-PEI function)
(C:027192)
In 2.5 version, the EG choice in the administration
transaction of VA Pacbase was used to manage the
generated entities.
This function is restored in 3.5 version by the LEG choice.
But in a first time, the screen can be consulted only.
The update will be available with the change 29001.
To display this list, enter the following input in the
CHOICE fields:
CH: LEG.....
The LEG command must be followed by the short code of the
generation environment and by the entity type.
The environment short code is on 2 characters.
The entity type is on 1 to 3 characters and can have
the following values: P (program); O (screen); B (DBD);
D (copys) ; YCS (eBusiness application) ; YDO (Folder); YSI
(initialization server) ; YMC (communication monitor)
YCE (Elementary component).
ex: LEGDEP
By default, the first found environment code and the Program
entity type are displayed.

For each entity generated in the selected generation
environment and the database context library, the screen
displays:
. its external name,
. the user who has requested the generation,
. the corresponding session number,
. the generation date.
If, moreover, the entity has already been put into
production, the screen displays:
. the user who has requested the production turnover,
. the production session number,
. the date of the production turnover,
. the mode of the production turnover.

PUPM: Purge procedure with save of the last
generation trace for BASIC environments
(C:028248)
For BASIC environments, a purge procedure keeps only the
trace of the last generation of the entity, in all
production sessions (ex-PEI functions).
The transactions output of the generation must first be
transferred into the repository.

Harmonization of the default codes (Environment,
Application) of the retrieval and the generation
(C:028331)
Harmonization of the default codes (Environment,
Application) of the retrieval and of the generation.
The procedure used to retrieve PEI data initializes the
default environments and applications with '*' characters
as it is done in the generation.
The BVPPP25 procedure retrieves the 2.5 PP file of PEI to
update the VA Pac development database.

EXPM: extraction of entities even if the SCM
Environment is created in a higher level library
(C:028387)
EXPM: extraction of entities even if the SCM Environment is
created in a higher level library.
An entity generated and associated with an SCM environment
is extracted even if this Environment is created in a
higher level library.

UPPM: The processing of a large number of
transaction abnormally ends. Corrected.
(C:028630)
UPPM: If a large number of transactions stored in QJ had
to be processed, the procedure abnormally ended because
the limit of the communication area was exceeded.
Corrected.

SCM entities controls in the batch procedures
(C:028913)

The checks performed in the batch procedures on the
SCM transactions are removed as the transactions
are considered as correct because they are extracted
from Developer workbench.
This concerns the UPDT, UPDP and REST (REC option)
procedures.

HIPM procedure: management of SCM records
(C:029314)

Upon PEI retrieval, environments were created with a
'BASIC-type configuration' and a 'basic'-type management.
As a consequence, as for PEI, only the latest production
turnover session of an instance is kept.
Globally, the production turnover information is
saved in the session frozen via the HIPM procedure.
With a 'basic'-type management, all the records which
correspond to a previous production turnover are deleted.
In the opposite case, all this data is kept, so a historical
account of production turnovers is made possible.

Be careful: the HIPM procedure must be re-installed
as the length of the SR and TR files has changed.

HIPM: duplicate generation of transaction lines.
Corrected.
(C:029320)
HIPM: duplicate generation of the transactions to be put
into production if the environment included more than one
Definition in the VA Pac Libraries network.
The error has been corrected.

PP25: if there is a request for update in session 1, a list
of the managed entities is loaded by default
(C:029485)
PP25: if the user requests the update of the environements
in session 1 and in inter-library mode, a list of the
managed entities is loaded by default.
Programs, Dialogs, DBS and copy will be managed by
these environments.
Upon the retrieval, the environement management tool is
loaded with 'BASIC'.

The display of information in the LEG screen
varies according to the SCM authorizations
(C:029529)
The display of information in the LEG screen
varies according to the SCM authorizations
The SCM authorization level is indicated in the
Administrator workbench, in the Profile or User browser.
It can have one of the following values:
'0' : no authorization
'1' : read only
'2' : update
'3' : administrator
The database-specific authorizations have
priority over the global authorizations.
The user-specific authorizations have priority over the
authorizations assigned in the Profile.
Users with a '0' authorization level cannot enter the LEG
choice.
Users with a '1' authorization level cannot perform any
update.

LEG choice screen: The PF7 function key is
operational
(C:029566)
On the LEG choice screen, the PF7 use correctly inhibits
the implicit updates.

LEG screen: modification of the fields displayed.
(C:029567)

LEG screen:
- Generation part:
The session type corresponds to the context of the
generation request, i.e. ' ' for the current session,
'H' for the initial session and 'T' for the test frozen
session.
- Production part:
The session status is no longer displayed. Only the session
number is important.
The production date is the date of the session freeze.
- Transfer result:
When an entity is transferred, the indicator of a pending
production is also transferred.

LEG: The display of the copy data is now correct.
(C:029619)

LEG: The display of the copy data whose online choice is
LEGDED has been modified.
The screen which displays the list of the copy data
related to an environement is now correct.

SCM/LEG: Paging problem corrected.
(C:029951)

SCM/LEG: Paging problem corrected.
The paging is now correct on the LEG screen.
The same entity is not displayed twice when the page
changes.

LEG choice: the on-line help is now available
(C:029960)

LEG choice: the on-line help is now available

SCM management of authorizations - LEG screen
(C:029965)

SCM management of authorizations - LEG screen
YC1 xxxx TUI screen: this screen will be accessible
in read-only mode, whichever the user authorization is
(message: UPDATE NOT AUTHORIZED)
The creation (update) of an environment will be possible
through the Administrator workbench only.

LEG screen:
To be able to delete a line from this screen, the user
will have to be assigned an SCM update authorization
and the update authorization on the work library.

Some data is wrongly reinitialized if
generation in 'T' or 'H' session
(C:029969)
For a generation in a 'T' or 'H' session:
a/ The GPPM procedure:
- wrongly reinitializes the production turnover data.
This data has not been passed on when the Log has been
written into the QJ file.
- wrongly repositions the status 'production in wait'
for the entity.
b/ The SIPM procedure does not position the production
turnover data.
Corrected.

EXPU: The number of lines in the prod. turnover
hist. account of an entity is limited in a Lib.
(C:029970)
EXPU: Now the number of lines in the production turnover
historical account for each entity is limited in a
Library.

HIPM: Identical session number for the production
turnover and the database freeze
(C:030038)
HIPM: Identical session number for the production
turnover and the database freeze
The session number of the production turnover is the same
as that of the database freeze if the database has not yet
been accessed for consultation or update that day.

Search Function

The result of a keyword search can now be
displayed on the 17 available lines of the screen
(C:029296)
The result of a keyword search can now be displayed on all
the available lines of the screen (17).
The 'keyword search' screen of version 3.N displays
the same number of lines and has the same behavior as that
of version 2.N.
The 17th line is not always displayed. It is displayed only
if the 16th line displays the first line of the entity
(entity code, name) and if a continuation line is required.
Otherwise, the display stops on the 16th line.

Segment

-CE of Segment: correct entering of the continuat.
of a long initial value in the 'UPD/TRGET' column
(C:028139)
-CE of Segment: the entering of the continuation of a long
initial value in the 'UPD/TRGET' is correct.

After entering a 'W' in the CONT column (under the T),
the entering of the continuation of the long initial value
in the 'UPD/TRGET' is correct, and the code of the data
element does not appear at the end of the column.

Controls for the creation of a Segment in a
protected library.
(C:029875)
Controls for the creation of a Segment in a protected
library.
If the library is defined with the protection of extracted
entities or no modification of extracted lines, the
creation of a Segment is authorized if its Data Structure
exists in the same library and if the Segment does not
exist in a protected library of the network.

Sub-network Comparison Utility

GBIR: take into account the change number
specified on the input card of CPSN
(C:028725)
GBIR: take into account the change number specified on the
input card of CPSN.
Corrected.

CPSN: table boundary violation in user entities
management
(C:029049)
CPSN: table boundary violation in user entities management.
A table containing all the extension user entities of the
master database was filled in by all the user entities
(client and extension).
A number of U.E. higher than 1000 generated a table
boundary violation.
This table must be changed at VINS procedure execution and
not with a standard CPSN.

GBIR: Initialization of fields useless for
subnetworks comparison.
(C:029185)
When comparing subnetworks, Program entities were
generated due to an error.
Some fields of the data are now correctly initialized and
these programs are no longer generated.

CPSN: when a text was deleted, the sort of
transactions was not correct.
(C:029221)
Now, the transactions for text deletion are sorted
by CPSN procedure as follows:
- deletion of text descriptions,
- deletion of the description 'L' line, corresponding to
the division title,
- deletion of the definition screen.
The definition is deleted lastly.

CPSN: management of implicit and explicit
action codes
(C:029224)
CPSN: management of implicit and explicit action code.
The implicit update of description of screen (-CE) generated
the creation of 000 lines.
Corrected.

Until now, when a CPSN was executed:
-in case of explicit update (option 2, position 33 or 34
of the CPSN card), the '&' characters were considered as
blanks (C or M actoin code)
- in case of implicit update (option 1, position 33 or 34
of the CPSN card that generates an X action code), the
'&' characters were considered as significative characte
Novelty:
For an explicit update, take into account the significative
'&' (for example in the data element label) and distingu
them from the '&' used as blanks (example: in the 'pare
element' field of a non child data element).
This has been corrected.

CPSN: process the deletions before the creations
for some cases of input aid call
(C:029247)
CPSN: process the deletions before the creations for some
cases of input aid call
If an entity calls two different input aids in two networks
or if in one network the -G is an input aid call and in the
other network, a comment line, the deletion of the slave
network transaction must be generated before the creation
of the master network transaction.
Corrected.

CPSN: incomplete data elements keywords
formatting
(C:029262)
CPSN: incomplete data elements keywords formatting.
The keywords of data elements are not processed if the
data elements definitions are the same in the master and
in the slave files.

CPSN: deletion of data element duplicate keywords
(C:029380)

CPSN: deletion of data element duplicate keywords.
Some data elements' keywords were processed twice but others
were not processed at the end of CPSN.
Corrected.

CPSN: management of the input and output formats
of Data Elements
(C:029942)
CPSN: management of the input and output formats
of Data Elements
When the three formats of a Data Element are identical in
a master network but different in a slave network, the
input and output formats of the master Data Element must
become the new formats of the slave Data Element.
Corrected.

CPSN: If formatting request for UPDT, correct
processing of continuation lines if large volumes.
(C:029973)
CPSN: if a formatting was requested for UPDT, the MV file
became incoherent when records including continuation lines
were processed.
The incoherence occurred right after the processing of a
very large amount of records.
This problem upon the writing of the MV file is now
corrected.

SQL Langage

SQL Block Description: the number of lines
recognized upon generation has been increased.
(C:028615)
In the 'Generation Elements' screen (-DRnnnGG) of an SQL
Database Block Description, the total number of lines
entered in each group (between
'... INSERTION BEGINNING < ---' and '... INSERTION END < ---')
and recognized upon generation has increased from 100 to 200.

Non assigned macro containing SQL orders
(not all) == incorrect generation
(C:028767)
Non assigned macro containing SQL orders.
The processings of this macrostructure are now correctly
assigned on the calling program.

In the SQL orders, the format of data elements
having an extended date format is no more truncate
(C:029068)
In the SQL orders, the format of data elements
having an extended date format is no more truncated.
In the generated F80 functions, some lines associated with
data elements having an extended date format specified on
their 'element description' screen might be truncated.
This has been corrected.

All the relational names are recognized when
SQL accesses are generated
(C:029283)
All the relational names are recognized when SQL accesses
are generated:
- All the 'SQL-Data Element' entered on a Segment -GG
are replaced with all their relational names and not only
with their first relational name.

The selected sub-schemas are recognized when
calling an SQL Data Structure in the -W screen
(C:029410)
The selected sub-schemas are recognized when
calling an SQL Data Structure in the -W screen
The sub-schema is now recognized for the generation of
SQL statements.

Syntax error in the OnLine Systems Development
generated code (REDFINES)
(C:029481)
Generated code with the BREAKDATE option: there is no
compilation error any more. The REDFINES clause is correctly
generated.

The Additional View Description for the standard
SQL functions is correctly generated.
(C:029491)
OnLine Systems Development generated code:
All the sub-functions (F80) which use the SQL declarations
entered in the Segment 'SQL View Description' screen are
correctly generated.

SQL generation error if Segment on a -CD cont'.
line and Block code not indicated in EXTERNAL NAME
(C:029704)
SQL generation error if the Segment was called on a
continuation line of a Program -CD and if the Block name
was not repeated in the EXTERNAL NAME field.

Now if a DB2 Segment is called in a Program -CD on a
continuation line, and if the Block name (in EXTERNAL NAME)
is entered only on the main line, the SQL statements will
be correctly generated.

Generation of SELECT without the FROM clause
when this clause is on the left of the -GG
(C:029768)
OnLine Systems Development: the FROM clause is recognized
in the SELECT generation, even if it is located on the
left of the Segment -GG screen.
This generation is identical to the batch generation.

Procedural language

It is impossible to modify the -P of a
Program in some cases of GP display (random error).
(C:024704)
It is impossible to modify the -P screen of
a Program in some cases when the GP screen
is displayed. The error has been corrected.

Miscellaneous : Online

It is impossible to modify the -P of a
Program in some cases of GP display (random error).
(C:024704)
It is impossible to modify the -P screen of
a Program in some cases when the GP screen
is displayed. The error has been corrected.

Deletion of a loop in the -PG display
(C:028084)

Deletion of a loop in the -PG display:
When a function 20, 25, 35 or 60 of a screen entity contains
more than 150 subfunctions, the message
'MAX NUM OF SUB-FUNCTIONS EXCEEDED : PRESS ENTER FOR MORE'
is sent to display the generated functions of the next
function.

Correction of the screen branching problem on the
description (-CE) of a segment with documentation
(C:028414)
Pressing "Enter" on the -CE of a segment branched on the
comment (-G) of the last data element in the page when this
latter had an associated comment (-G), instead of branching
on the continuation page of the -CE.
This problem has been corrected.

Loop on the GP screen display in C2 option
(C:028753)

When, in the JCL lines (GP - C4 option), there was a
999999 line which was the 36th, the request of
the validated lines (C2 option) generated a loop.
Corrected.

The 'B' action code on a continuation line of -CP
did not delete the line
(C:028833)
The 'B' action code on a continuation line of -CP did not
delete this continuation line.
This has been corrected.

You can set the cursor on an entity code in the
GP screen.
(C:028869)
You can set the cursor directly on a line in the
GP screen.
Structure of the command:
GP and then the GPRT command on 4 positions and then the
entity code.
Blanks between the command and the entity must be filled in
with '&'.
Example: GP GCP&PGMXXX

Online mode: The display of some screens was
erroneous after a UE definition display
(C:029184)
Online mode: The display of some screens was erroneous
after a U.E. definition display.
The entity label displayed in a description screen was
not correct if previously an access was made to a User
Entity having the same code.
This has been corrected.

LNE choice: display with option C2
(C:029191)

In option C2, the choice LNE displays correctly the code
of a Data Element, the code of the Parent Data Element
and the usage.

Management of errors on the VA Pacbase sign-on
screen
(C:029361)
VA Pacbase sign-on screen: the numericity control on the
session is now correctly performed.

Screen branching on the X-refs of an Input Aid
in a C1 view is now correct
(C:029373)
On-line mode: the screen branching on the cross-references
of an Input Aid in a C1 view is now correct.

The customization of function keys no longer
disturbs the screen branching in a screen -SIM
(C:029598)
The use of function keys can be customized in VA Pac via
the REST procedure. This customization no longer disturbs
the screen branching simulation.

With the 'From...' choice on a Meta-Entity U.E.
list, conversion into uppercase (FxxxL , 1xxxLY)
(C:029622)
With the 'From...' choice on a Meta-Entity U.E.
list, conversion into uppercase (FxxxL , 1xxxLY)

If the 'uppercase' option (related to the U.E. code)
has been specified on a Meta Entity, the characters entered
after L or LY to view the list from a code are conve
into upper case letters.

HS and HO sub-menus: -Gx for the documentation,
help, generation and options
(C:029643)
In the HS and HO sub-menus, the -Gx line is now
titled 'documentaion, help, generation and options' because
'Gx' is sub-divided into GC, GE, GG, GO.

GP screen: Refresh of the screen after the
submission of a job.
(C:029649)
GP screen: After a job is submitted, the screen is
correctly refreshed.

Utilities

MCI operator: all the 'MOVE' will be generated,
even on occursed fields.
(C:029517)
The MCI operator generates a series of 'MOVE' on all the
fields which have the same code, from one group to another
group.
In this context, if one of the operands includes an index,
this index '(nn)' will be generated for all the fields of
this operand.

Entity Lock

A user cannot delete an entity having a technical
lock
(C:028996)
An entity downloaded in the Workstation for an update cannot
be deleted, even by the user who has downloaded it.

LL choice: Now the duplication of a line does not
take the technical lock into account.
(C:030003)
LL choice: Now the duplication of a line does not
take the technical lock into account.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

VisualAge Pacbase
VisualAge Pacbase Server

Software version:

3.5

Operating system(s):

AIX, Linux, Solaris, UNIX

Reference #:

1251581

Modified date:

2014-06-04

Translate my page

Machine Translation

Content navigation