VisualAge Pacbase Windows 3.5 V05X E

Preventive Service Planning


Abstract

List of changes of the VisualAge Pacbase Windows 3.5 V05X version

Content

VISUALAGE PACBASE Windows 3.5 V05X

Warning: the index management has been modified.
Hence a reorganization for both the administration
(ROAD) and the development (REOR) databases is required.
The reorganization must precede the installation of
the model (D08META and I05META).

NEW FUNCTIONALITIES

Administration

The Access Key displays the current number
of active seats for the Build facility
(C:029455)
The Access Key now displays the current number of active
seats for the Build facility, in addition to the Update
facility.

Activation of new key -
New batch and online management
(C:031007)
New UKD0 procedure
: Preparation of UKD1
This procedure can run while the online access remains open.
Input:
A standard identification line
A line to indicate the key to be activated
- This line is optional
If it is not specified, the last 'archive' key, whose
expiration date is still valid, will be taken into account.

Output:
Input file for UKD1
Execution report

Improved UKD1 procedure

New user input for key activation
- Use rights' assigning lines (manually entered or output
by UKD0)
This implies that the procedure can run with changed
'targets'.
If the number of existing permanent licenses is greater than
the 'n' number of the licenses of the new key, then
the first 'n' permanent licenses found are kept.

Activation of the new key via ADWorkbench

Principle identical to UKD1 (same rule for permanent rights)
The update (transfers of User and Profile rights
according to the matching entered) is now deported but it
is transparent to the user ...

Batch System Development

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 (Date data
elements can be broken down into elementary fields).

New generation limit for GCP and GCD: a segment
can now contain 9999 data elements
(C:030231)
Generation of programs or copy clause.
For the generation, a segment can now contain up to 9999
data elements (before, the limit was 999).
The number of input lines in the -CE of the segment has not
been modified.
An error message is printed in the GPRT output report if
this limit has been exceeded.
The segment statistics screen (-STA) now correctly displays
the counters.

Key, license

The Access Key displays the current number
of active seats for the Build facility
(C:029455)
The Access Key now displays the current number of active
seats for the Build facility, in addition to the Update
facility.

Activation of new key -
New batch and online management
(C:031007)
New UKD0 procedure
: Preparation of UKD1
This procedure can run while the online access remains open.
Input:
A standard identification line
A line to indicate the key to be activated
- This line is optional
If it is not specified, the last 'archive' key, whose
expiration date is still valid, will be taken into account.

Output:
Input file for UKD1
Execution report

Improved UKD1 procedure

New user input for key activation
- Use rights' assigning lines (manually entered or output
by UKD0)
This implies that the procedure can run with changed
'targets'.
If the number of existing permanent licenses is greater than
the 'n' number of the licenses of the new key, then
the first 'n' permanent licenses found are kept.

Activation of the new key via ADWorkbench

Principle identical to UKD1 (same rule for permanent rights)
The update (transfers of User and Profile rights
according to the matching entered) is now deported but it
is transparent to the user ...

UKD1: Rights can be assigned to Profiles
(C:031008)

UKD1: Rights can be assigned to Profiles
In addition to the 'U'-type lines which are used to
assign rights to Users, 'P'-type lines can now be used
to assign rights to Profiles.
col 1 on 1 : P
col 2 on 20 : Profile code to be updated
From col 22 : Rights to be assigned
(on 5 characters, 10 are possible)
on 4 char : type of right to be assigned (PA1, IW1, CO1,
LE1, T11, T21, TM1, E11, E21, EM1 , ...)
on 1 char : permanent assignment (1 if permanent, space
otherwise)

The rights assigned to a Profile can also be assigned to
all the Users who have this Profile, provided these rights
are compatible with those already assigned to the User.

Similarly, if a permanent right is assigned, the permanent
character is assigned to the Profile. However it is assigned
to the User only if the authorized number is not exceeded.

Client/Server system develop.

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 (Date data
elements can be broken down into elementary fields).

Client/Server system dev. 3.x

Timeout on an XA transaction
(C:029495)

A new parameter has been added to the Definition of a
Communication Monitor. This parameter enables you to specify
the server timeout. It is numeric and contains 6
characters maximum.
It applies to the XA communication type and the Tuxedo
code to generate.

Personalization

In 'C2' option, the label of entities linked by
relation in a user entity will not be displayed
(C:030324)
In 'C2' option, the label of entities linked by relation in
a user entity will not be displayed.

Generators

Unicode taken into account in a limited way
(C:028823)

Unicode taken into account in a limited way.

The Unicode is taken into account in a limited way, the
specifications and limits will be detailed in a Technote
put on the VisualAge Pacbase Support Internet site.

Option to prevent the execution of the GPRT
job follow-up in the LB database
(C:030235)
Option to prevent the execution of the GPRT
job follow-up in the LB database
The job follow-up written in the LB database is a
basic functionality of the GPRT procedure or the
JOB function.
A new option has been created to enable the user to inhibit
this follow-up. It can be specified in the input
line of the REST restoration procedure (col. 13) with
the following values:
'0' : no inhibition of the job follow-up
'1' : inhibition of the job follow-up
If the option is missing in the database, it is set up to
'0'.
If the option is missing in the REST procedure input, the
last value of the option in the database is retrieved.

Generated programs

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 (Date data
elements can be broken down into elementary fields).

New generation limit for GCP and GCD: a segment
can now contain 9999 data elements
(C:030231)
Generation of programs or copy clause.
For the generation, a segment can now contain up to 9999
data elements (before, the limit was 999).
The number of input lines in the -CE of the segment has not
been modified.
An error message is printed in the GPRT output report if
this limit has been exceeded.
The segment statistics screen (-STA) now correctly displays
the counters.

Workbench - Global

The access authorizations on the various
interfaces are consistent
(C:029562)
With AD workbench, you can now download entities
which contain data from higher-level libraries on which
you have no authorization.

Metamodel

Existence check of a segment called in -CD or -W
(F), -CP of prog, screens and eBusiness entities
(C:011674)
Existence check of segments called in -CD, -W (F), -CP
of programs, screens and eBusiness entities.

The Segments must now be created before being called in
the -CD of screens, -CP and -W (F-type) of programs,
screens or eBusiness entities.
All these uses must be deleted before the segment deletion.

Server : On-line, Batch, Parm

Monitoring tool for the management of the
listeners on Windows
(C:030400)
An executable program, TP.exe, can be used to display the
status of the clients connected to a server identified by
the socket number used.
This utility is launched via:
TP.exe <SocketNb_Server>

Middleware

Timeout on an XA transaction
(C:029495)

A new parameter has been added to the Definition of a
Communication Monitor. This parameter enables you to specify
the server timeout. It is numeric and contains 6
characters maximum.
It applies to the XA communication type and the Tuxedo
code to generate.

On-Line System Development

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 (Date data
elements can be broken down into elementary fields).

Pacbase Access Facility

Optimized access to the LOCKS Table
(C:030513)

The access to the LOCKS Table has been optimized when a
condition bears on both the type and the code of an entity:
there is a direct access to the entity, and no longer to the
lock.

This change applies to the pre-processor as well as to the
4 PAF extractors for the TIMESTAMP and LOCKS Tables.
It also applies to the PAF dictionary since the format of
a column has been modified (OTIM/OHEU has been changed from
8 to 6 char.).

Batch Procedures

A counter of long data is included in the SAVE
and REOR reports
(C:028853)
A counter of long data has been added in the SAVE
report (step PTU520: PAC7EW report) and in the REOR reports
(step PTU200: PAC7EE report, input long data, and
step PTU240: PAC7IE report, output long data).
This also applies to the SVAD and ROAD procedures.

Improvement of the UTMP procedure
(C:030143)

Improvement of the UTMP procedure.
A user input has been added:
*-line with User code, password, option to refresh the
password of users that already existed in 3.N version.
The structure of the line is as follows:
! Pos.! Length! Value ! Signification
! 2 ! 1 ! '*' ! Line code
! 3 ! 8 ! uuuuuuuu ! User code
! 11 ! 8 ! pppppppp ! Password
! 27 ! 1 ! '1' ! Retrieval of the password even
! ! ! ! if the user already exists
! ! ! blank ! Retrieval of the password only
! ! ! ! if the user does not exist

The passwords refresh depends on the option chosen in the
user input.

Performance of sequential processing on database
VSAM files: use of AMP instead of LSR
(C:030512)
To improve the processing time, the AMP option replaces
the LSR option in appropriate cases (PACS, SAVE, MLIB, PACG)

Implementation of the 'Consolidated Tracing
Facility' on MicroFocus versions > 4.0
(C:030748)
Implementation of the 'Consolidated Tracing Facility' (CTF)
on Microfocus.
This facility is available only on Microfocus versions
higher than 4.0.
It enables the user to improve the trace mode, should
a problem occur upon the execution of a procedure.
So when the Trace mode is activated via the
BVPTrace variable set to YES, the Consolidated Trace
Facility is activated for the programs indicated in the
CTF configuration file: mftrace.cfg.
This file is supplied in the INSTDIR\Server\Config
directory. The user must modify it to add the name of the
program to be traced.
The result of the bvptrace.txt trace is automatically
calculated when the procedure is launched. It is located in
the directory which contains the procedure execution report.
Any modification of the mftrace.emitter.textfile
parameters must then be avoided.
All the information about the setting of parameters in
this configuration file can be found at the following
address in the Micro Focus site:
http://supportline.microfocus.com/Documentation/books/sx40sp2/sgpubb.htm

Retrieve

PC25: An Input Aid is assigned the correct type,
even if only its Definition exists
(C:030511)
PC25: An Input Aid is assigned the correct type,
even if only its Definition exists
An Input Aid without a description used to take on the type
of the last description processed (which then belonged to
another Input Aid).
Now after the retrieval, an Input Aid takes on the 'Comment'
type if it does not have a description.

Runtime

Installation with Rollback: Microfocus Server
for COBOL 5.0 is now recognized
(C:030710)
Installation : Microfocus Server
for COBOL 5.0 is now recognized

Software Config. Management

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.

Security Systems Interface

TUI access: the user code can be different
from the system sign-on user code.
(C:030144)
TUI access: the user code can be different
from the system sign-on user code.
In Administrator workbench, in the security browser, a new
tab allows to specify the authorization to connect with
a user code different from the system one for a database
under RACF control.
On the sign-on screen of VisualAge Pacbase, if the database
is under RACF control, the user code and password can be
entered if the authorization to connect with another user
is set in the security browser.

The cursor is positioned on the Library field of
the sign-on screen if the RACF interface is used
(C:030521)
From now on, when the RACF interface is used, the cursor
is positioned on the Library field of the sign-on screen
even if the option to authorize the user code modification
is set up.

Segment

Existence check of a segment called in -CD or -W
(F), -CP of prog, screens and eBusiness entities
(C:011674)
Existence check of segments called in -CD, -W (F), -CP
of programs, screens and eBusiness entities.

The Segments must now be created before being called in
the -CD of screens, -CP and -W (F-type) of programs,
screens or eBusiness entities.
All these uses must be deleted before the segment deletion.

Procedural language

Existence check of a segment called in -CD or -W
(F), -CP of prog, screens and eBusiness entities
(C:011674)
Existence check of segments called in -CD, -W (F), -CP
of programs, screens and eBusiness entities.

The Segments must now be created before being called in
the -CD of screens, -CP and -W (F-type) of programs,
screens or eBusiness entities.
All these uses must be deleted before the segment deletion.

Miscellaneous : Online

Unicode taken into account in a limited way
(C:028823)

Unicode taken into account in a limited way.

The Unicode is taken into account in a limited way, the
specifications and limits will be detailed in a Technote
put on the VisualAge Pacbase Support Internet site.

Modification of the update for a .M choice
(C:030072)

The .M command in the choice field used to automatically
transform lowercase letters into uppercase letters
(especially in P lines). Now the letters remain unchanged.
Moreover the positioning attributes of the Data Structure,
which have been defined in the program's flowchart in AD
workbench, are also kept.

TUI access: the user code can be different
from the system sign-on user code.
(C:030144)
TUI access: the user code can be different
from the system sign-on user code.
In Administrator workbench, in the security browser, a new
tab allows to specify the authorization to connect with
a user code different from the system one for a database
under RACF control.
On the sign-on screen of VisualAge Pacbase, if the database
is under RACF control, the user code and password can be
entered if the authorization to connect with another user
is set in the security browser.

The cursor is positioned on the Library field of
the sign-on screen if the RACF interface is used
(C:030521)
From now on, when the RACF interface is used, the cursor
is positioned on the Library field of the sign-on screen
even if the option to authorize the user code modification
is set up.

CORRECTED BUGS

Journal Statistic Utility

ACTI: the session number in the statistics screen
is now displayed on 5 characters
(C:030410)
Actually, the number appeared in an 8-char internal format.

The 'C' value (particular on-line input mode
movements) is now possible for the &INPT parameter
(C:030597)
The 'C' value (particular on-line input mode
movements) is now possible for the &INPT parameter.

ACTI: the parameters' labels are correctly
returned in the prints
(C:030642)
In the Analysis of Activity module (ACTI procedure), the
values associated with the parameters are now returned
with the correct label instead of the internal code.

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.

Initialization of the password validity duration
in the security browser
(C:030164)
Initialization of the password validity duration in the
security browser.
In the supplied administrator database, the indicator of
password validity duration is now checked to "unlimited"
and the field "Number of validity days" is protected.

The V04 Administration model can be installed
on versions < V03 without any error
(C:030291)
VING: Installation of the Administration model
Errors could occur when installing on databases whose
version was earlier than V03.
This has been corrected.

Control of the password entered in TUI mode.
Special characters are rejected.
(C:030618)
Now the input of a new password in TUI mode is checked and
special characters ($, *,...) are not authorized.
The only characters authorized are: digits from 0 to 9,
alphabetical characters (uppercase and lowercase), the blank
and the '/' characters.

The origin of a Use Right is lost after this
Right is used
(C:031053)
In Administrator workbench, when you request the display
of a User's Rights, the origin of this Right (the Profile
code) is displayed in the browser after its creation.

On the other hand, when this Right is used, the date of
its last use is recorded on the Right, but its origin
(Profile code) used to disappear.
This bug has been corrected: the Profile code is no
longer erased by the use of the Right.

Batch

UPDT: when a definition with a keyword is deleted,
the timestamp is deleted
(C:030099)
UPDT: when a definition with a keyword was deleted, the
timestamp was wrongly kept.
It is now deleted.

UPDT: Printing and recycling grouped transactions
(C:030358)

UPDT: Printing and recycling grouped transactions.

Some transactions of the MB file in input of the UPDT
procedure are grouped in order to obtain an update
transaction in the MV file.

The update output report now print the whole transactions
in input.
In case of error on a group transaction, its elements are
written in the recycled transactions file.

UPGP: Optimized calls to the control sub-program
when Users are being updated
(C:030425)
UPGP: Optimized calls to the control sub-program
when Users are being updated

Batch System Development

Correct management of the '.' back to the MCI
operator in the batch and online generators
(C:028648)
Correct management of the '.' back to the MCI operator for
the GCP and GCO generations.

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 / CASE OF: the values input after the
'IT' are no more truncated
(C:030040)
GCP / CASE OF: the values input after the 'IT' are no
more truncated.
The IT instruction that follows the CASE OF is now
generated on 2 lines in order to avoid the truncation
problems.

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 Program (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 options in the -GO screen of a database block
do not trouble the generation anymore
(C:030190)
The options in the -GO screen of a database block
do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an
associated block (specified in the 'EXTERN' field) with at
least one option in its -GO screen, the generated program
was incomplete (segments of the -CD and specific processing
not generated):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option
(-GO of the block) was ignored when it was preceded by an
option.
This is also corrected.

GCP / Incomplete Segment generation
(C:030217)

GCP / Incomplete Segment generation

If a Segment (S1) contains Data Elements with an initial
value ('V' in column T (CONT) in the Segment -CE) and if
another Segment, before S1, contains a Data Element
with a value control ('E' in column T (CONT) in the Segment
-CE), S1 is not fully generated in the generated code of
the Program (GCP) which calls it: the generation stops at
the Data Element just before the first Data Element which
contains a 'V' value. The Segments which follow S1 are
not generated either.
This has been corrected.

GCO: Occursed Data Elements are generated again
in Segments whose organization is '2'
(C:030380)
GCO: Occursed Data Elements and the associated SQL indicator
are generated again in Segments whose organization is '2',
even if the DESCR=ALL option has not been indicated in the
corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a
DB2 Segment is generated again.

Generators - date processing - Correction of
various problems
(C:030423)
Generators - date processing - Correction of
various problems:
1 - For all the operators and condition types related to
dates, the working fields can be up to 30 characters long
(they are no longer truncated).
Moreover, if the date format is not specified, it is
now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly
processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer
truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to
put the condition on 2 lines.

Generation of 2 Programs, from 2 different
Libraries, which call the same Segment
(C:030497)
Generation of 2 Programs, from 2 different Libraries,
which call the same Segment.
If you generate, in the same flow, two Programs from
two Libraries (without any hierarchical link) and if these
Programs call the same Segment, the description of this
Segment is correctly generated in the second Program.

Erroneous format in the Report Call of Elements
of a batch Program
(C:030543)
Erroneous format in the Report Call of Elements
of a batch Program.
The Data Elements with a signed format (1st character = S)
are no longer generated as X(8) in the Report Call of
Elements of a Program.

A message is printed if a generated Program
calls a 'transaction' DS with + 999 Elements
(C:030556)
GPRT: A message is printed upon the generation of a
Program which calls a 'transaction' Data Structure
with more than 999 Data Elements.

GPRT / GCP: If a Program calls a Data Structure whose usage
is 'transactions (not to) be validated' ('M' or 'N' usage
in the -CD), and if the Segment calls more than
999 Data Elements, an error is printed in the report
(PAC7ID), at the beginning of the flow.

Incorrect generation of segments in T or X
(table) use
(C:030613)
Incorrect generation of segments in T or X (table) use -
(New generation limit for GCP and
GCD: a segment can now contain 9999 data elements).
In a table, the common part is now correctly generated
before the specific part.

The CO operator (Case Of) generated date breakdown
(day, month, year) on the Procedural Code
(C:030680)
The CO operator (Case Of) used to generate the date
breakdown (day, month, year) on the Procedural Code if
the last Data Element of the last Segment processed was a
date ...
This has been corrected.

Incorrect generation of Programs with override
of Macro lines - Change 28767 continued
(C:030715)
Incorrect generation of Programs with override
of Macro lines - Change 28767 continued
For a Program which contains non-assigned Macro Structures
only, the specific lines which override Macro lines
are now correctly generated again.

GCO and GCP with 'Cobol formatting option': 150
lines possible in a Cobol paragraph
(C:030720)
With the 'COBOL formatting option' on the Library
Definition, up to 150 lines are possible in a COBOL
paragraph (between two periods), in the batch or OLSD
module.

Formatted dates in Report Description: the
separator is now correctly managed again
(C:030884)
Formatted dates in Report Description: the separator was
not correctly managed.
The generation of dates in Report Descriptions ('operation
on source field' = '0', '1' or '2' followed by a line with
an 'operation on source field' = 'U') is now correct.
DATSEW is loaded with DATSEP or DATSET before the perform
of the date processing function (F9520).

'Date' data element wrongly generated in working
if -CD resources in P/R access and organization 2
(C:030954)
'Date' data element wrongly generated in working
if -CD resources in P/R access and organization 2.

If the -CD choice screen of a program contains 2 segments in
'P'- (principal) and 'R'-usage (result) and if those 2
segments have a '2'-organization, the DAT8G or DAT8S1G data
element is no more generated in working.

Connection

Initialization of the choices sent to the server
when launching Administrator Workbench
(C:031266)
Initialization of the areas which are used to format the
choice sent to the server when loading the Meta-Entities of
Administrator Workbench.
This initialization impacts the first connections of
Administrator Workbench to an IMS z/OS repository.

Client/Server system develop.

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.

Comm. monitor and folder manager: the record
number in the work file can be higher than 999
(C:030186)
The communication monitor and the folder manager manage
records with a number higher than 999.

The options in the -GO screen of a database block
do not trouble the generation anymore
(C:030190)
The options in the -GO screen of a database block
do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an
associated block (specified in the 'EXTERN' field) with at
least one option in its -GO screen, the generated program
was incomplete (segments of the -CD and specific processing
not generated):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option
(-GO of the block) was ignored when it was preceded by an
option.
This is also corrected.

The session number is correctly filled in when
generating an 'S'-type Screen via the GVC command
(C:030337)
When generating an 'S'-type Screen via the GVC command, the
field which corresponds to the session number is correctly
filled in.

GVC - version number on the ECR line no more
truncated
(C:030819)
The version number (5-characters) entered in the options
(-GO, NUVERS option) is correctly filled in on the ECR line
of the GVC.

GGC: In the message 'LENGTH OF COMPLEMENTARY AREA
MUST BE: nnnn', nnnn is 5 characters long
(C:031087)
GCO and GGC: in the error message 'LENGTH OF COMPLEMENTARY
AREA MUST BE: nnnn', the field is now 5 characters long.

Management of the request number in the driving
record of the work file
(C:031123)
For an application without any user buffer, the request
number in the driving record of the work file is set to 1.

Business Component and Oracle: a date present in
the WHERE clause is complemented with TO_DATE.
(C:031257)
In a Business Component which accesses an Oracle Database,
the date-formatted fields present in the WHERE clause are
complemented with TO_DATE.

Client/Server system dev. 3.x

Unisys Communication Monitor - Folder Manager with
a RDMS database: INCLUDE SQLCA wrongly generated
(C:028674)
Unisys 2200 Communication Monitor and Folder Manager
with a RDMS database:
The INCLUDE SQLCA clause was wrongly generated in the
Communication Monitor and in the Folder Manager. And, in
the Folder Manager, the SQLCODE declaration was wrongly
missing.
This has been corrected.

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.

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 cursor 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).

Close of the work file conditioned by its
effective open
(C:030056)
The close of the work file is correctly performed if this
file has been opened and if an access error has been
detected in the processing continuation.

Database Block (DDL)

Type of line in the -Gx screens that does not
involve a generation
(C:029940)
It is possible to define, in complement, '*'-type lines
in the -GC, -GG, -GE and -GO choice screens. These lines are
processed like comments.
In Batch, these lines are VC, VG, VE or VO lines with a
'*'-type.

PF11 branching on a database block description
and on a segment
(C:030109)
For the database blocks and segments, the PF11 function key
allows to branch on the generation elements.

Block -DR: updating an I- or J-type line
deletes the -DRnnnK
(C:030203)
Block -DR: updating an I- or J-type line
deletes the -DRnnnK.

Let us consider an I-type line (numbered nnn) on a
Relational Block description (-DR) in which you have entered
the key's Data Elements (-DRnnnK). (Note that a + is
displayed at the end of the line).
If you modify this line (ex: is you enter 'U' in the
'Key Type' column), the key's Data Elements are no longer
deleted (Note that the + is still displayed).

B......GN...: The SQL return code is not displayed
after a request for a catalog updating.
(C:030383)
B......GN...: The SQL return code is not displayed
after a request for a catalog updating.
This has been corrected.

GCB: In a Block generated code, there are no
longer quotes in the Segment name.
(C:030475)
GCB: In a Block generated code, there are no longer
quotes in the Segment name.
In the generated code of a Block, the quotes in the
value of the 'record-type Element' are now replaced with
blanks, according to the value of the delimiter indicated
on the Library Definition.

Erroneous control cards in front/back
and generation of SQL Blocks
(C:030735)
Erroneous control cards in front/back
and generation of SQL Blocks
An unknown control card in front of flow no longer inhibits
the generation of the next Blocks in the flow of requests.
In some cases, an unknown control card in front of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
In all cases, an unknown control card in back of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
A generation request without any control card in front/back
no longer inherits the control cards in front/back of the
preceding request.

Dictionary

Screen Description: The label length is reset if
a called Data Element is not a label
(C:029311)
If a label-type Data Element is called in a Screen
Description, the length of this label is stored in the
record.
If a label is replaced with a Data Element which is not
a label, the stored length is now reset to zero.
Because this field was not reset, the CPSN procedure or
the '.M' choice used to detect discrepancies.
Since this field is not an input field, the update was
ineffective.

Improved management of technical locks
(C:029857)

Technical lock on a Screen Description:
- This lock is visible on the Definition,
- Another user can modify the Definition but also all the
Descriptions which are not locked.
- A message is displayed if the Description is locked.

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.

LXE command: the update timestamp of a Data
Element is no longer recognized as a use
(C:030202)
LXE command: the update timestamp of a Data
Element is no longer recognized as a use.
When a Data Element only has an update timestamp, without
any other use, it is displayed in the 'List of unused Data
Elements and Properties' (LXE generation/print command).

The .S choice on an -XP screen in Z1 view
stopped on the first line found
(C:030318)
The .S choice on an -XP screen in Z1 view
stopped on the first line found.
The problem came from the fact that the search was not
performed on the -XP lines of a library sub-network.
This is now corrected.

The error 6157 ('THE ENTITY CODE MUST NOT
CONTAIN BLANKS') is changed into a warning
(C:030363)
The error 6157 is now changed into a warning and the message
is:
'THE ENTITY CODE CONTAINS BLANKS'.

Updates of input aid are rejected when the
modification of extracted elements is forbidden
(C:030793)
PUF: all the update transactions of an input aid call
are rejected when the modification of extracted elements is
forbidden (for segments and data structures).

PacDesign Methodologies

VINS: Update of the methodology Meta Entities in
inter-library mode
(C:030560)
VINS: Update of the methodology Meta Entities in
inter-library mode. (for Microfocus or Acucobol environment)
Updating Meta Entities in inter-Library mode is now
possible even if these Meta Entities already exist in a
lower-level Library.

VINS, installation of methodologies: deletion
of the Methodology entities in Libraries.
(C:030567)
VINS, installation of methodologies: deletion
of the Methodology Meta-Entities in all Libraries.
The installation of Methodologies must be performed in
session 1 and in inter-library mode.
At the same time, the Methodologies which already exist
in various Libraries are now correctly suppressed.
Moreover, the error 6456C no longer appears upon a VINS
installation.

eBusiness Module

Comm. monitor and folder manager: the record
number in the work file can be higher than 999
(C:030186)
The communication monitor and the folder manager manage
records with a number higher than 999.

Personalization

Input of User Entities: protection against
Low-Values
(C:030892)
The low-values resulting from the 'End-of-Field deletion'
and 'Character deletion' will be replaced with blanks.

Generators

Type of line in the -Gx screens that does not
involve a generation
(C:029940)
It is possible to define, in complement, '*'-type lines
in the -GC, -GG, -GE and -GO choice screens. These lines are
processed like comments.
In Batch, these lines are VC, VG, VE or VO lines with a
'*'-type.

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.

SCM: The number of generation commands processed
in the same run is now extended to 9999
(C:030367)
SCM: A crash occurred when the number of generation commands
exceeded 1000 in the same run. This number is now extended
to 9999.

CCF/CCB of a GCD: The parameters of the '*' line
are valorized if GCD submitted with GSQ
(C:030646)
CCF/CCB of a GCD: The parameters coming from the '*' line
were not valorized if the GCD command was submitted with
the GSQ command (ex: lib, session and user code of the
'L' parameter).
This has been corrected.

Incorrect generation of Programs with override
of Macro lines - Change 28767 continued
(C:030715)
Incorrect generation of Programs with override
of Macro lines - Change 28767 continued
For a Program which contains non-assigned Macro Structures
only, the specific lines which override Macro lines
are now correctly generated again.

GCO and GCP with 'Cobol formatting option': 150
lines possible in a Cobol paragraph
(C:030720)
With the 'COBOL formatting option' on the Library
Definition, up to 150 lines are possible in a COBOL
paragraph (between two periods), in the batch or OLSD
module.

Erroneous control cards in front/back
and generation of SQL Blocks
(C:030735)
Erroneous control cards in front/back
and generation of SQL Blocks
An unknown control card in front of flow no longer inhibits
the generation of the next Blocks in the flow of requests.
In some cases, an unknown control card in front of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
In all cases, an unknown control card in back of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
A generation request without any control card in front/back
no longer inherits the control cards in front/back of the
preceding request.

Generated programs

Correct management of the '.' back to the MCI
operator in the batch and online generators
(C:028648)
Correct management of the '.' back to the MCI operator for
the GCP and GCO generations.

Unisys Communication Monitor - Folder Manager with
a RDMS database: INCLUDE SQLCA wrongly generated
(C:028674)
Unisys 2200 Communication Monitor and Folder Manager
with a RDMS database:
The INCLUDE SQLCA clause was wrongly generated in the
Communication Monitor and in the Folder Manager. And, in
the Folder Manager, the SQLCODE declaration was wrongly
missing.
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.

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 system message is now correctly displayed
for a Dialogue
(C:029486)
In order to correctly display a system message displayed in
the case of an abend, the F81ER has been modified as
follows:
F81ER. MOVE S-WWSS-PROGE TO D-SERR-PROGE.
MOVE S-WWSS-XFILE TO D-SERR-XFILE.
MOVE S-WWSS-XFUNCT TO D-SERR-XFUNCT.
MOVE S-WWSS-STATUS TO D-SERR-STATUS D-STAT-FILST.
IF D-STAT-CHAR1 = '9' MOVE D-STAT-CHAR1 TO D-STAT-DIS
MOVE LOW-VALUE TO D-STAT-CHAR1
MOVE D-STAT-BIN TO D-STAT-DIS4
MOVE D-STAT-DISPL TO D-SERR-STATUS.
MOVE D-SERR-LINE1 TO D-SERR-DISP. *
DISPLAY D-SERR-DISP WITH BLANK SCREEN. *
GOBACK.
F81ER-FN. EXIT.

The 2 lines with a * have been modified.
These modifications impact a Dialogue with a 'type of Cobol
to generate' set to 3.

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

GCP / CASE OF: the values input after the
'IT' are no more truncated
(C:030040)
GCP / CASE OF: the values input after the 'IT' are no
more truncated.
The IT instruction that follows the CASE OF is now
generated on 2 lines in order to avoid the truncation
problems.

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

Close of the work file conditioned by its
effective open
(C:030056)
The close of the work file is correctly performed if this
file has been opened and if an access error has been
detected in the processing continuation.

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 Program (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 options in the -GO screen of a database block
do not trouble the generation anymore
(C:030190)
The options in the -GO screen of a database block
do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an
associated block (specified in the 'EXTERN' field) with at
least one option in its -GO screen, the generated program
was incomplete (segments of the -CD and specific processing
not generated):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option
(-GO of the block) was ignored when it was preceded by an
option.
This is also 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.

GCO of 2 Screens in the same flow: interference on
the SQL accesses described on the Segment -GG
(C:030212)
GCO of 2 Screens in the same flow: interference on
the SQL accesses described on the Segment -GG.

Let us consider an S1 Segment with an N1 customized access
described in the generation elements (-GG).
This S1 Segment is called in 2 screens: SC0001 and SC0002.
In SC0001, this N1 customized access is called in function
80.
In SC0002, this N1 customized access is not called in
function 80.
If you generate both these screens in the same flow, the
N1 customized access will no longer appear in the F80 of
SC0002.

GCP / Incomplete Segment generation
(C:030217)

GCP / Incomplete Segment generation

If a Segment (S1) contains Data Elements with an initial
value ('V' in column T (CONT) in the Segment -CE) and if
another Segment, before S1, contains a Data Element
with a value control ('E' in column T (CONT) in the Segment
-CE), S1 is not fully generated in the generated code of
the Program (GCP) which calls it: the generation stops at
the Data Element just before the first Data Element which
contains a 'V' value. The Segments which follow S1 are
not generated either.
This has been corrected.

The session number is correctly filled in when
generating an 'S'-type Screen via the GVC command
(C:030337)
When generating an 'S'-type Screen via the GVC command, the
field which corresponds to the session number is correctly
filled in.

C30231 follow-up - Erroneous segment gener. (GCP)
if segment select. = common part + specific part
(C:030373)
Erroneous segment generation (GCP) if the segment selection
contains the common part and the renamed specific part.

The data elements of the common and specific parts were
wrongly mixed (first data element of the specific part back
to the first data element of the common part, second data
element of the specific part back to the second data
element of the common part, etc.)
This has been corrected. In the generated Cobol, first
appear all the data elements of the common part, followed by
all the data elements of the specific part.

GCO: Occursed Data Elements are generated again
in Segments whose organization is '2'
(C:030380)
GCO: Occursed Data Elements and the associated SQL indicator
are generated again in Segments whose organization is '2',
even if the DESCR=ALL option has not been indicated in the
corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a
DB2 Segment is generated again.

Generators - date processing - Correction of
various problems
(C:030423)
Generators - date processing - Correction of
various problems:
1 - For all the operators and condition types related to
dates, the working fields can be up to 30 characters long
(they are no longer truncated).
Moreover, if the date format is not specified, it is
now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly
processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer
truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to
put the condition on 2 lines.

The quotes of the value of a Segment 'record-type
Element' are replaced with blanks
(C:030437)
The quotes of the value of a Segment 'record-type
Element' are replaced with blanks.
In the generated code of a screen, the quotes of the
value of the 'record-type Element' are now replaced with
blanks, according to the value of the delimiter indicated
on the Library Definition.

GCB: In a Block generated code, there are no
longer quotes in the Segment name.
(C:030475)
GCB: In a Block generated code, there are no longer
quotes in the Segment name.
In the generated code of a Block, the quotes in the
value of the 'record-type Element' are now replaced with
blanks, according to the value of the delimiter indicated
on the Library Definition.

Generation of 2 Programs, from 2 different
Libraries, which call the same Segment
(C:030497)
Generation of 2 Programs, from 2 different Libraries,
which call the same Segment.
If you generate, in the same flow, two Programs from
two Libraries (without any hierarchical link) and if these
Programs call the same Segment, the description of this
Segment is correctly generated in the second Program.

GCO / an initial value is recognized for a numeric
protected field
(C:030528)
GCO / an initial value is recognized for a numeric
protected field.
If an initial value is specified for a numeric protected
field ('F' nature), then the loading of this initial value
is generated in the F8115 subfunction.

When DATSEP and DATSET are explicitly set, they
are no longer overwritten (AD, AD0, AD1, AD2)
(C:030537)
When DATSEP and DATSET are explicitly set, they
are no longer overwritten (AD, AD0, AD1, AD2).

WARNING ! The date processing function (F9520 for the batch
function and F8120 for the other generators) uses a new
field for the separator: DATSEW.

In the generation of the AD, AD0, AD1, AD2 operators, the
separator is correctly set: with the separator
included in the date, if any, or with DATSEP (dates with an
E or M format) or DATSET (dates with a G format) otherwise.

Erroneous format in the Report Call of Elements
of a batch Program
(C:030543)
Erroneous format in the Report Call of Elements
of a batch Program.
The Data Elements with a signed format (1st character = S)
are no longer generated as X(8) in the Report Call of
Elements of a Program.

A message is printed if a generated Program
calls a 'transaction' DS with + 999 Elements
(C:030556)
GPRT: A message is printed upon the generation of a
Program which calls a 'transaction' Data Structure
with more than 999 Data Elements.

GPRT / GCP: If a Program calls a Data Structure whose usage
is 'transactions (not to) be validated' ('M' or 'N' usage
in the -CD), and if the Segment calls more than
999 Data Elements, an error is printed in the report
(PAC7ID), at the beginning of the flow.

Incorrect generation of segments in T or X
(table) use
(C:030613)
Incorrect generation of segments in T or X (table) use -
(New generation limit for GCP and
GCD: a segment can now contain 9999 data elements).
In a table, the common part is now correctly generated
before the specific part.

Dialogue: Some generated lines concerning
the UNISYS-A generation were wrong
(C:030637)
Dialogue: Some generated lines concerning
the UNISYS-A generation were wrong.
An adaptation of some lines containing the character 'à'
to be transformed in '@' could also modify the lines
structure.
The generated code was erroneous.
This has been corrected.

The CO operator (Case Of) generated date breakdown
(day, month, year) on the Procedural Code
(C:030680)
The CO operator (Case Of) used to generate the date
breakdown (day, month, year) on the Procedural Code if
the last Data Element of the last Segment processed was a
date ...
This has been corrected.

DBD: NOT NULL WITH DEFAULT does no more contain
the initial values if the CONT column is set to S
(C:030714)
DBD : NOT NULL WITH DEFAULT does not contain anymore the
values of the VALUE/SFC column if the CONT column is set to
'S'.

GCO and GCP with 'Cobol formatting option': 150
lines possible in a Cobol paragraph
(C:030720)
With the 'COBOL formatting option' on the Library
Definition, up to 150 lines are possible in a COBOL
paragraph (between two periods), in the batch or OLSD
module.

Generation of Oracle database block: the clause
NOT NULL WITH DEFAULT is no more generated
(C:030815)
The clause NOT NULL WITH DEFAULT is no more generated for
the ORACLE database blocks.
And, the value to be checked is not taken into account for
any block type.

GVC - version number on the ECR line no more
truncated
(C:030819)
The version number (5-characters) entered in the options
(-GO, NUVERS option) is correctly filled in on the ECR line
of the GVC.

SQL/SERVER generation: the initial value for
NOT NULL DEFAULT depends on the column type
(C:030820)
Generation of SQL SERVER Database Blocks:
The initial value to be entered for NOT NULL DEFAULT now
varies according to the column type.

Formatted dates in Report Description: the
separator is now correctly managed again
(C:030884)
Formatted dates in Report Description: the separator was
not correctly managed.
The generation of dates in Report Descriptions ('operation
on source field' = '0', '1' or '2' followed by a line with
an 'operation on source field' = 'U') is now correct.
DATSEW is loaded with DATSEP or DATSET before the perform
of the date processing function (F9520).

10*R FF00: if the access type is not indicated,
all the access functions to FF00 are replaced
(C:030914)
On-Line Systems Development generator:
F80 10*R FF00: if the access type is not indicated, all the
access functions to FF00 are now replaced.

'Date' data element wrongly generated in working
if -CD resources in P/R access and organization 2
(C:030954)
'Date' data element wrongly generated in working
if -CD resources in P/R access and organization 2.

If the -CD choice screen of a program contains 2 segments in
'P'- (principal) and 'R'-usage (result) and if those 2
segments have a '2'-organization, the DAT8G or DAT8S1G data
element is no more generated in working.

The recognition of the MCI operators is effective
on subprograms
(C:030958)
MCI operators:
The recognition is done in all the subprograms whatever
the syntax used in the PROCEDURE DIVISION clause (with or
without USING ...)
Modification of the BVPUTMCR program return codes:
- 00 : MCI operator found
- 04 : MCI operator missing (warning)

GGC: In the message 'LENGTH OF COMPLEMENTARY AREA
MUST BE: nnnn', nnnn is 5 characters long
(C:031087)
GCO and GGC: in the error message 'LENGTH OF COMPLEMENTARY
AREA MUST BE: nnnn', the field is now 5 characters long.

PTEX: In the PIAXDOC Table, the CENT column
contains the called entity
(C:031097)
In the generation of an Extraction Master Path, PIAXDOC
Table, the CENT column contains the called entity code.

GCO: A dot is generated before the F8125-FN tag
if the last Data Element has an 'F' nature
(C:031105)
GCO: A dot is generated before the F8125-FN tag
if the last Data Element has an 'F' nature

GCO: correct generation of map with simple quote
for the LINUX generator toward IMS
(C:031120)
GCO: correct generation of map with simple quote for the
LINUX generator toward IMS.

Management of the request number in the driving
record of the work file
(C:031123)
For an application without any user buffer, the request
number in the driving record of the work file is set to 1.

Business Component and Oracle: a date present in
the WHERE clause is complemented with TO_DATE.
(C:031257)
In a Business Component which accesses an Oracle Database,
the date-formatted fields present in the WHERE clause are
complemented with TO_DATE.

Generation

DCR: Report code on 3 characters
(C:029327)

In the ENTITY field of a DCR command, you must now enter
a Report code on 3 characters to select one Report, or
blanks to select all the Reports.
Note:
Since there is no retrieval of the commands already created
in the previous versions, the user will have to
manually modify these commands before submitting the job.

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.

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 submitted in on-line
mode.
Protection on the LB file if a job is submitted in online
mode and retrieved according to the operating system for a
batch submission of GPRT.

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.

Corrections of bugs in GP screen
(C:029896)

Corrections of bugs in GP screen
With option 1:
- If a command with a continuation line was deleted while
another command with a user error (for example '2' in the
continuation line number) was simultaneous created, the
deleted command, as well as its continuation line, were not
reset to blank. Moreover, the 'd' action code was still
displayed on the deleted command line.
- If a command with continuation lines was duplicated and
if the entity code was erroneous (unknown entity for
example), the error 'E' was positioned on the last
continuation line instead of on the first command line.

With option 2:
- JP choice as well as screen recalls (Rn) did not work
for the GP screen with the option 2.
- The commands validated on a screen previous to the
job submission screen were not recognized by the JOB
function (ex: the screen contained GCO SCREEN1. The
command GCP PGM1, even if validated on the previous
screen, was not recognized by the JOB function).
- When trying to update the screen, the screen used to be
displayed again with a one-line shift (now updates are
ignored and the next screen is displayed, as it is
indicated in the warning 'TYPE OF DISPLAY NOT ALLOWING
UPDATE').

With option 4:
- An alphanumeric line number caused the display of an
unknown error message
(ERROR MESSAGE NOT FOUND, KEY:FMVUT10CC000)
- The error 'E' was not positioned on the erroneous line
(the action code remained blank).
- Modification of a JCL line + PF7 in order to inhibit the
update
error wrongly displayed ('EXPLICIT UPDATE: INVALID
ABSENCE OF MOVEMENT CODE).
- If there was an error on the lines following those
already updated, the lines already deleted were not reset to
blank and the explicit transaction codes (d, m, c) were
still displayed on the screen whereas updates had been
correctly performed.

All this has been corrected.

Management of the continuation line on a GSQ
generation command
(C:029945)
Management of the continuation line on a GSQ generation
command.
If the parameters of a before/after card are entered on a
continuation line, for the GSQ command, those parameters
are now correctly operated.

BVPACAGP launching: the User directory (Rep_USR)
passed as a parameter is protected by double quote
(C:031205)
In the INIT.vbs file of the SYS\PROC directory, the
User directory (Rep_USR), passed as a parameter when
BVPACAGP is launched, is now protected by double quotes.
This allows using directory names with spaces in them, as
is the case with the default value "C:\Program Files".

Database management

PACS-MLIB: MLIB can be run in simulation mode if
files are open to online use (Unix & Windows Rep.)
(C:028771)
The PACS - MLIB procedure can be executed for a simulation,
even if files remain open to online use.

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.

The reorganization procedure (REOR) filters
erroneous data
(C:030522)
If the session number of a record is greater than the
current session number, this record is not taken into
account.
It will appear in the report of step PTU200, with the
following error message: INVALID SESSION.

Graph

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

Message 'NO ENTITY OF HIGHER LEVEL' wrongly
displayed when xrefs were deleted with Pacdesign
(C:030617)
The message 'NO ENTITY OF HIGHER LEVEL' is no longer
displayed when cross-references are deleted with
Pacdesign.

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 'documentation, help, generation and options' because
'Gx' is sub-divided into GC, GE, GG, GO.

The documentation of LL screen no longer mentions
the fields removed since version 2.5
(C:030944)
The documentation of the 'LL' screen no longer mentions
the fields removed since the version 2.5 (ST, L and X).

Local Mapping

Screen mapping: An update could occur when exiting
the screen, accessed in read mode
(C:030037)
Screen mapping: An error could occur when exiting
the screen, accessed in read mode
When exiting a Screen Mapping, an untimely update could
occur.
This has been corrected;

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: a $ttDxx with an entity linked to a $/Ytt
equal to the $/YttDEF one is now correct
(C:027696)
A $/YttDxx extraction with a $/Ytt type linked
entity equal and with the same link in the
$/YttDEF is now correct : before correction, the
value of the linked field in the description was
the one in the definition.
Corrected.

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.

A new description of a Meta-Entity can be
created (in character mode)
(C:029282)
A new description of a Meta-Entity can be created, even
if this Meta-Entity is used.

Now a description of a Meta-Entity can be created or
modified in online mode if none of the User Entities
related to this Meta-Entity contains a line of this
description.
Until now, as soon as a User Entity was created from the
Meta-Entity, a control used to inhibit the creation of a
new description on this Meta-Entity.
This control has been refined.

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.

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 converted
into upper case letters.

UTM2: the label of the old relation is retrieved
in case of transformation into new relation
(C:030080)
UTM2: If an old relation is changed into a new relation,
its label is kept.

User entities: warning if areas cannot be
displayed in online mode
(C:030082)
When the description of user entities is displayed in online
mode, if the remaining place on the line is not enough to
completely display the following data, a warning is
displayed.

EXPU: Search of entities to be purged on a
user entity call type
(C:030087)
PACX-EXPU: Search of entities to be purged on a user entity
call type.
According to the other Pacbase entities, it is now possible
to logically or physically purge user entities
(excluding random data).
The search is performed by specifying '$' or 'Y' in column
'7' of the user input and the meta entity call type in
position '14'.
If the entity type is not specified, the search is performed
on all entity types of the database.

$/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).

UTM1: limitation of the -CR extraction to the
processed relation
(C:030111)
UTM1/UTM2: limitation of the -CR extraction to the processed
relation.
When an entity called, for a same line number, different
relations in different sessions, UTM1 wrongly extracted, for
each relation, all the records (-CR) corresponding to this
line number, including data that concerned other relation
codes.
The extraction is now limited to the processes relation.

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) and has an impact
on the batch and online extractors.

LOCKS: a selection on both a $/Ytt entity type
and the entity code is now possible
(C:030264)
LOCKS: a selection on both a $/Ytt entity type
and the entity code is now possible even if this
entity is just after another user entity in the
LL screen for the same user.

No more improper repetition of fields in a user
entity description
(C:030316)
No more improper repetition of fields in the extraction of
a user entity description after an access by PAF to the
definition of this user entity.

Meta Entity: call of a Data Element defined more
than once in the network if its format is the same
(C:030347)
The description of a Meta Entity can call a Data
Element defined more than once in the Libraries network
if its format is always identical in these various
Libraries.
In this case, the 8488E error message will no longer be
displayed.
Note:
The preprocessor has been modified. The user programs
processing with the CMEDEL and EMEDEL tables must be
regenerated and reprocessed.

After PC25 retrieval, the descriptions of
Meta Entities can be aligned
(C:030375)
After the retrieval, the description of a Meta Entity,
defined in various Libraries, can be aligned.
A Meta Entity will be chosen as the reference (master).
The same Meta Entity (target), which exists in another
network, can be modified in order to be the image of the
master Meta Entity.
The internal identifiers of the Data Elements which are
common to the master and the target will be aligned.
Only modifications will be performed: if the target
description is more complete, it will remain as
such.
If Data Elements of the master Meta Entity are not called in
the target Meta Entity, the descriptions of the target
will not be completed.
The User Entities of the modified target Meta Entity will
also be modified.
You must perform the following operations:
- Save the Database
- Extract the master Meta Entity via EXTR with the
CPSN format
- Modify the target Meta Entity and its UE via Vins.
In the VINS user input, you must indicate:
. the Library of the target Meta Entity
. 'F' in column 33

Assignment of Text lines: The User Entities whose
identifier is 6 char. long max. may not exist
(C:030399)
Assigning Text lines to a User Entity which does not
exist is now possible if the identifier of this User
Entity is 6 characters long maximum.

Correct deletion of an old UE which contains a
Data Element (x(6) format) linked to a Segment
(C:030408)
An old UE which contains a Data Element (x(6) format)
linked to a Segment via a Relation can now be
deleted without any problem.
This change also applies to the Data Elements linked
to Reports or Data Structures.

UPDT on extension or client UE: the Descriptions
were wrongly converted into uppercase
(C:030504)
UPDT: Now this procedure takes into account the value of the
'Uppercase' field of the Meta Entity.

UTM2: The error '9006' is no longer displayed
when it applies to a Relation
(C:030505)
UTM2: During the update, the error '9006' (creation of
a record which already exists) is no longer displayed if
the entity of the record is a Relation.
These existing records are not updated but no error message
is sent.

Warning upon the creation of a UE already
present in a lower-level library
(C:030834)
When creating a User Entity already present in a lower-level
library, the following message was not displayed:
'ENTITY TO BE CREATED BUT ALREADY EXISTING IN A SUB-LIBRARY'
This is now corrected.

The extraction of a User Entity Description is
now correct, whatever the SIZE value
(C:030959)
The extraction of a User Entity Description is now correct,
whatever the value of the SIZE parameter, even when
the content of a called Data Element linked, via a Relation,
with another User Entity is empty.

This change applies to the batch and online extractors only
and the client programs do not need to be reprocessed.

REOR: created deletion index
(C:031083)

In the meta entity description, it is possible to remove the
use of a relation (set to blank).
In that case, the linking indexes of this relation
are correctly removed by the REOR procedure.

The PAF extraction of the User Entities'
Descriptions sends the lines in the correct order
(C:031225)
The PAF extraction of the User Entities'
Descriptions sends the lines in the correct order

This change applies to the PAF pre-processor and to both
the PAFB10 and PAFT10 extractors.

!!! It is required to re-preprocess the user programs for
all the $/YTTDxx (description) tables. !!!

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.

Keywords

An extraction on the WORDSEARCH table no longer
causes a return code 31 on the SYSPAF
(C:031086)
An extraction on the WORDSEARCH table no longer
causes a return code 31 on the SYSPAF.

On-Line System Development

Correct management of the '.' back to the MCI
operator in the batch and online generators
(C:028648)
Correct management of the '.' back to the MCI operator for
the GCP and GCO generations.

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 !!!

Screen Description: The label length is reset if
a called Data Element is not a label
(C:029311)
If a label-type Data Element is called in a Screen
Description, the length of this label is stored in the
record.
If a label is replaced with a Data Element which is not
a label, the stored length is now reset to zero.
Because this field was not reset, the CPSN procedure or
the '.M' choice used to detect discrepancies.
Since this field is not an input field, the update was
ineffective.

The system message is now correctly displayed
for a Dialogue
(C:029486)
In order to correctly display a system message displayed in
the case of an abend, the F81ER has been modified as
follows:
F81ER. MOVE S-WWSS-PROGE TO D-SERR-PROGE.
MOVE S-WWSS-XFILE TO D-SERR-XFILE.
MOVE S-WWSS-XFUNCT TO D-SERR-XFUNCT.
MOVE S-WWSS-STATUS TO D-SERR-STATUS D-STAT-FILST.
IF D-STAT-CHAR1 = '9' MOVE D-STAT-CHAR1 TO D-STAT-DIS
MOVE LOW-VALUE TO D-STAT-CHAR1
MOVE D-STAT-BIN TO D-STAT-DIS4
MOVE D-STAT-DISPL TO D-SERR-STATUS.
MOVE D-SERR-LINE1 TO D-SERR-DISP. *
DISPLAY D-SERR-DISP WITH BLANK SCREEN. *
GOBACK.
F81ER-FN. EXIT.

The 2 lines with a * have been modified.
These modifications impact a Dialogue with a 'type of Cobol
to generate' set to 3.

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 options in the -GO screen of a database block
do not trouble the generation anymore
(C:030190)
The options in the -GO screen of a database block
do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an
associated block (specified in the 'EXTERN' field) with at
least one option in its -GO screen, the generated program
was incomplete (segments of the -CD and specific processing
not generated):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option
(-GO of the block) was ignored when it was preceded by an
option.
This is also 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.

GCO of 2 Screens in the same flow: interference on
the SQL accesses described on the Segment -GG
(C:030212)
GCO of 2 Screens in the same flow: interference on
the SQL accesses described on the Segment -GG.

Let us consider an S1 Segment with an N1 customized access
described in the generation elements (-GG).
This S1 Segment is called in 2 screens: SC0001 and SC0002.
In SC0001, this N1 customized access is called in function
80.
In SC0002, this N1 customized access is not called in
function 80.
If you generate both these screens in the same flow, the
N1 customized access will no longer appear in the F80 of
SC0002.

GCO: Occursed Data Elements are generated again
in Segments whose organization is '2'
(C:030380)
GCO: Occursed Data Elements and the associated SQL indicator
are generated again in Segments whose organization is '2',
even if the DESCR=ALL option has not been indicated in the
corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a
DB2 Segment is generated again.

Generators - date processing - Correction of
various problems
(C:030423)
Generators - date processing - Correction of
various problems:
1 - For all the operators and condition types related to
dates, the working fields can be up to 30 characters long
(they are no longer truncated).
Moreover, if the date format is not specified, it is
now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly
processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer
truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to
put the condition on 2 lines.

The quotes of the value of a Segment 'record-type
Element' are replaced with blanks
(C:030437)
The quotes of the value of a Segment 'record-type
Element' are replaced with blanks.
In the generated code of a screen, the quotes of the
value of the 'record-type Element' are now replaced with
blanks, according to the value of the delimiter indicated
on the Library Definition.

GCO / an initial value is recognized for a numeric
protected field
(C:030528)
GCO / an initial value is recognized for a numeric
protected field.
If an initial value is specified for a numeric protected
field ('F' nature), then the loading of this initial value
is generated in the F8115 subfunction.

Dialogue: Some generated lines concerning
the UNISYS-A generation were wrong
(C:030637)
Dialogue: Some generated lines concerning
the UNISYS-A generation were wrong.
An adaptation of some lines containing the character 'à'
to be transformed in '@' could also modify the lines
structure.
The generated code was erroneous.
This has been corrected.

GCO and GCP with 'Cobol formatting option': 150
lines possible in a Cobol paragraph
(C:030720)
With the 'COBOL formatting option' on the Library
Definition, up to 150 lines are possible in a COBOL
paragraph (between two periods), in the batch or OLSD
module.

10*R FF00: if the access type is not indicated,
all the access functions to FF00 are replaced
(C:030914)
On-Line Systems Development generator:
F80 10*R FF00: if the access type is not indicated, all the
access functions to FF00 are now replaced.

GCO: A dot is generated before the F8125-FN tag
if the last Data Element has an 'F' nature
(C:031105)
GCO: A dot is generated before the F8125-FN tag
if the last Data Element has an 'F' nature

GCO: correct generation of map with simple quote
for the LINUX generator toward IMS
(C:031120)
GCO: correct generation of map with simple quote for the
LINUX generator toward IMS.

Va Pacbase/DSMS Interface

The DSMS control file is no longer assigned in
the REST and RESY restoration procedures
(C:030222)
The DSMS control file is no longer assigned in
the REST and RESY restoration procedures.
When the archived transactions are retrieved, since the
DSMS controls are not carried out, assigning the
'DC' control file is pointless.

GP with option C4: update authorized by DSMS
(C:030805)

DSMS always authorizes the update of the JCL lines displayed
in the GP screen with option C4.

The DSMS V2.5 controls on User Entities are
correctly interpreted
(C:030814)
The DSMS V2.5 controls on User Entities are
correctly interpreted
With DSMS V3.5, the controls on User Entities are carried
out on the long identifier.
To ensure the compatibility with the version 2.5 which
controlled these entities on their short codes,
the type of the code controlled is now indicated.

Pacbase Access Facility

PAF: a $ttDxx with an entity linked to a $/Ytt
equal to the $/YttDEF one is now correct
(C:027696)
A $/YttDxx extraction with a $/Ytt type linked
entity equal and with the same link in the
$/YttDEF is now correct : before correction, the
value of the linked field in the description was
the one in the definition.
Corrected.

SEGDEL: 'I' view with a selection on a Data
Element called in a lower-level library
(C:028696)
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 $/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.

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

Extractions on DBDDS*GEN table are now correct
for the description line number CLINDC
(C:030116)
The CLINDC line number is now correctly
extracted during the FETCH and it's possible now
to make a selection on this line number.
Note:
The preprocessor has been modified. The user programs
processing with the DBDDS*GEN table must be regenerated
and reprocessed.

The extraction of Model entities via LOCKS Table
now returns 'REL', OBJ' or 'FIC' types
(C:030123)
The extraction of Model entities via LOCKS Table
now returns 'REL', OBJ' or 'FIC' types instead of 'MET'.
Note:
The preprocessor has been modified. The user programs
processing with the LOCKS table must be regenerated
and reprocessed.

SEGDEL Table: the extraction is now complete
if the -CE contains a group field named FILLER
(C:030135)
SEGDEL Table: the extraction is now complete
if the -CE contains a group field named FILLER
Note:
This change concerns the batch and online PAF extractors
only and the user programs do not have to be reprocessed.

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) and has an impact
on the batch and online extractors.

SESHIS table : the code of the production session
has been added (SESPRO)
(C:030146)
SESHIS table : the code of the production session has
been added (SESPRO).
This change needs a re-preprocess.

The PAF preprocess will now generate in multi-
screen variant option ('C') an EXEC CICS LINK
(C:030210)
The PAF preprocess will now generate in multi-screen
variant option ('C') an EXEC CICS LINK instead off a CALL
order.

DBDDSR: an extraction on this table is now correct
on a 'I' line with key data elements and comments
(C:030245)
DBDDSR: an extraction on this table is now correct
on a type 'I' line with key data elements (K screen)
and associated comments (-G... 2nd level).

SCRDEF cursor: the before/after cards of a
dialogue are now correctly extraction in 'I' view
(C:030255)
SCRDEF cursor: the before/after cards of a dialogue are
now correctly extracted in 'I' view on the definition
screen.

LOCKS: a selection on both a $/Ytt entity type
and the entity code is now possible
(C:030264)
LOCKS: a selection on both a $/Ytt entity type
and the entity code is now possible even if this
entity is just after another user entity in the
LL screen for the same user.

DSTDEF: the last character of the keywords field
in X(55) is no more truncated
(C:030269)
DSTDEF table: the last character of the keywords field
in X(55) is no more truncated.

DLGCMP: the selection on the dialogue code (with
inf. and sup. boundaries, or equality) is correct
(C:030288)
DLGCMP: the selection on the dialogue code (with
inferior and superior boundaries, or equality) is
now correct.
Note:
The preprocessor has been modified. The user programs
processing with the DLGCMP table must be regenerated
and reprocessed.

The errors found in the PAF pre-processor
no longer cause an ABEND
(C:030312)
The errors found in the PAF pre-processor no longer cause
an ABEND.
Note:
To take account this correction, the PAF user programs must
be regenerated and reprocessed.

No more improper repetition of fields in a user
entity description
(C:030316)
No more improper repetition of fields in the extraction of
a user entity description after an access by PAF to the
definition of this user entity.

SEGXCRLCAL: a selection on the type and code
of the linked entity now works fine
(C:030350)
SEGXCRLCAL: a selection on the type and code
of the linked entity now works fine.
Note:
The preprocessor has been modified. The user programs
processing with the SEGXCRLCAL table must be regenerated
and reprocessed.

The format of the linked entity code in all the
xxxCAL/CAE tables is now X(30)
(C:030352)
The length of the area corresponding to the CENT column
code could be 6 or 30.
Now, the CENT column code has a 30-characters length for
all the xxxCAL/CAE tables.
Note:
The preprocessor has been modified. The user programs
processing with the xxxCAL and xxxCAE tables must be
regenerated and reprocessed.

SEGDEL with an indicator equal to 'M' (multiple
key) : the Data Element level is now correct
(C:030385)
SEGDEL with an indicator equal to 'M' (multiple
key) : the missing information (Data Element level
and pictures) is now correctly extracted.

SEGDEL: if the -CE calls 2 contiguous identical
Data Element codes, both these codes are extracted
(C:030421)
SEGDEL: if the -CE calls 2 contiguous identical
Data Element codes, both these codes are extracted

Extraction of the ...X.RLCAL/CAE, ...CAL/CAE
tables with a relation to a segment gives 'SEG'
(C:030449)
The extraction of the ...X.RLCAL/CAE, ...CAL/CAE
tables with a relation to a segment gives 'SEG'
as the called entity type and no more 'DST'

An extraction about 'OLD' user entities will no
more look for the internal code
(C:030572)
As the old user entities always have a 6-characters code,
it is useless to look for the internal code (it is the
same as the long code).
Note:
The preprocessor has been modified. The user programs
processing with the $TTxxx and YTTxxx tables must be
regenerated and reprocessed.

From now on, the access to a description of user
entity after its definition in interlibrary is OK
(C:030787)
Description of the defect:
In a PAF extractor, after an access to a user entity
definition in library *** and in 'I' view, it was not
possible to access to one of its descriptions in a given
library.
This has been corrected.

The SIZE value will no more disturb extractions
on the DBDDSR PAF table
(C:030802)
The SIZE value will no more disturb extractions
on the DBDDSR PAF table.

An extraction on KYWDEF now returns all the data
concerning the keyword (type + definition)
(C:030835)
An extraction on KYWDEF now returns all data concerning the
keyword (type + definition)

SEGDEL: an extraction in 'I' inter-library
with a Segment call in the -CE is correct
(C:030861)
SEGDEL: an extraction in 'I' inter-library
with a Segment call in the -CE is correct

The pre-processing of a PAF program is identical,
whether it is generated in a flow or alone
(C:030873)
The pre-processing of a PAF program is identical,
whether it is generated in a flow or alone

KYWDEF table: the keywords type (synonyms,
definition) are now correctly filled in
(C:030885)
KYWDEF table: the keywords type (synonyms, definition) are
now correctly filled in.

TIMESTAMP Table: a selection on entity type, with
conditions on entity code, works fine
(C:030890)
TIMESTAMP Table: the entity type can be selected,
and Less Than or Greater Than conditions
can be specified on the entity code.
This change applies to the pre-processor and to the rout
PAF extractors (PAFB10, PAFT10, PAFBWS and PAFTWS).

Reminder: an extraction with the TIMESTAMP Table must always
include a condition on TENT and CENT (this is controlled).

LOCKS table: the column containing the entity type
and the entity code is now correctly extracted
(C:030945)
LOCKS table: the column containing the entity type and the
entity code is now correctly extracted.

The extraction of a User Entity Description is
now correct, whatever the SIZE value
(C:030959)
The extraction of a User Entity Description is now correct,
whatever the value of the SIZE parameter, even when
the content of a called Data Element linked, via a Relation,
with another User Entity is empty.

This change applies to the batch and online extractors only
and the client programs do not need to be reprocessed.

Modification of online PAF for the V3.5: correct
writing of SYSPAF file and documentation update
(C:030984)
Modification of online PAF for the V3.5: correct writing of
the SYSPAF file and update of the documentation.

An extraction on the WORDSEARCH table no longer
causes a return code 31 on the SYSPAF
(C:031086)
An extraction on the WORDSEARCH table no longer
causes a return code 31 on the SYSPAF.

PTEX: New choice //P I D in order to select
Input Aids' Descriptions
(C:031092)
XPAF: The choice //P Icpia D has been added in order to
select Input Aids' Descriptions

PTEX: In the PIAXDOC Table, the CENT column
contains the called entity
(C:031097)
In the generation of an Extraction Master Path, PIAXDOC
Table, the CENT column contains the called entity code.

PAF Tables: the session type is now 'T' if the
session is frozen
(C:031190)
PAF Tables: the session type is now 'T' if the
session is frozen

This change applies to the batch and online extractors for
the TIMESTAMP, LOCKS and FROZENSES Tables.
For the FROZENSES Table, the user program must be
re-processed since, for this table, the pre-processor
is impacted.

The PAF extraction of the User Entities'
Descriptions sends the lines in the correct order
(C:031225)
The PAF extraction of the User Entities'
Descriptions sends the lines in the correct order

This change applies to the PAF pre-processor and to both
the PAFB10 and PAFT10 extractors.

!!! It is required to re-preprocess the user programs for
all the $/YTTDxx (description) tables. !!!

The CMEDSE and EMEDSE Tables now extract each
Description only once
(C:031256)
The CMEDSE and EMEDSE Tables now extract each
Description only once. They used to extract each description
twice when there were child descriptions.
This change applies to the batch and online PAF extractors
for the CMEDSE and EMEDSE Tables (there is no need to
re-preprocess).

Personalized Document. Manager

All the lines of a PIA called in a -Gx screen
can now be printed in a Volume via a PTEx
(C:029542)
XPAF: It is now possible to print all the lines of an
Input Aid called in the Comments, Generation Options
or Generation Elements of an entity (-Gx).
On the PAF side, this change applies to both the batch and
online extractors, and to the pre-processor for all the
..DOC, ...OPT, ...GEN tables as well as
FICOBJDOC, DBDDS*DOC, DBDDS*GEN, OBJDELDOC, RELDELDOC,
SEGDELDOC, SEGDELGEN. For all these tables, the user
programs must then be re-processed.

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.

PTEX: New choice //P I D in order to select
Input Aids' Descriptions
(C:031092)
XPAF: The choice //P Icpia D has been added in order to
select Input Aids' Descriptions

PTEX: In the PIAXDOC Table, the CENT column
contains the called entity
(C:031097)
In the generation of an Extraction Master Path, PIAXDOC
Table, the CENT column contains the called entity code.

Pacbench Quality Control

PQC: The negation in a rule is now correctly
processed
(C:030719)
PQC: The negation in a rule is now correctly
processed

Batch Procedures

PACS-MLIB: MLIB can be run in simulation mode if
files are open to online use (Unix & Windows Rep.)
(C:028771)
The PACS - MLIB procedure can be executed for a simulation,
even if files remain open to online use.

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.

UTM2: a step to check the ME file issued from
UTM1 has been added
(C:029926)
UTM2: a step to check the ME file issued from UTM1 has
been added.
The ME file issued from the UTM1 procedure contains the list
of relation calls. Each relation must be linked to only one
entity type.
To guarantee the validity of this file, a control program
(ptume3) is added in the UTM2 procedure.
If several entity types are linked to a same relation, a
display is sent requesting the correction and the
re-execution of UTM2.

EXTR-CPSN: replacement of a comment line with an
Input Aid call line
(C:029930)
EXTR-CPSN: replacement of a comment line with an
Input Aid call line
If, in a library network, the -G is an Input Aid call and in
the second library network a comment line, the transaction
is deleted in the slave network before the transaction is
created in the master network.
This is 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.

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.

EXPU: Search of entities to be purged on a
user entity call type
(C:030087)
PACX-EXPU: Search of entities to be purged on a user entity
call type.
According to the other Pacbase entities, it is now possible
to logically or physically purge user entities
(excluding random data).
The search is performed by specifying '$' or 'Y' in column
'7' of the user input and the meta entity call type in
position '14'.
If the entity type is not specified, the search is performed
on all entity types of the database.

EXPU: on the report, the name of the Data Elements
which do not have a name is '--> CHILD ELEMENT'
(C:030093)
EXPU: on the report, the name of the Data Elements
which do not have a name of their own is '--> CHILD ELEMENT'
The child Data Elements whose names were those of their
parent Elements used to have a blank name in the output
report of the purge. Now, their names are
'--> CHILD ELEMENT', as it was in versions before
the 3.N.

UPDT: when a definition with a keyword is deleted,
the timestamp is deleted
(C:030099)
UPDT: when a definition with a keyword was deleted, the
timestamp was wrongly kept.
It is now deleted.

REOR procedure: the output report containing the
purged data is complete
(C:030119)
If the purge of non existing data is requested, these
are printed in the list of purged data with the
message 'NOT FOUND'.

EXLI: if several extractions are requested, the
context is correct for the child data elements
(C:030168)
EXLI: is several extractions are requested, the context is
correct for the child data elements.
If EXLI contained several input cards, the Pacbase context,
used to search information on the parent data element, could
be erroneous.
This has been corrected.

Optimization of the PJ25 and UV25 retrieval
procedures
(C:030209)
Optimization of the 2.5 -> 3.5 retrieval procedures:
- of the PJ file (BVPPJ25 procedure) by limiting the
accesses to the AE file
- of the UV file (BVPUV25 procedure) by limiting the
accesses to the AE file and deletion of the loop if the maxi
key is missing in the 2.5 UV file.

The DSMS control file is no longer assigned in
the REST and RESY restoration procedures
(C:030222)
The DSMS control file is no longer assigned in
the REST and RESY restoration procedures.
When the archived transactions are retrieved, since the
DSMS controls are not carried out, assigning the
'DC' control file is pointless.

UPDT-PAC7IE: The vertical and horizontal
characters of the Library are recognized
(C:030240)
The PAC7IE report of UPDT now recognizes the vertical
and horizontal characters indicated on the Library
Definition.
The PAC7ID report of GPRT now includes the labels PAGE,
ANOMALIES and the bottom frame in the list of commands.

UPDT: Incomplete transactions on keywords could
impair the update of timestamps
(C:030248)
UPDT: Incomplete transactions on keywords could
impair the update of timestamps.
If a header transaction for the update of an entity's
keywords was not followed by the transaction which contained
the keywords, it was ignored.
This could prevent the entity timestamp from being updated.
This is now corrected.

GPRT: The uses of an Input Aid are no longer
truncated in the DCI command
(C:030263)
GPRT: The uses of an Input Aid are no longer
truncated in the DCI command.
These fields, which are 75 characters long, were truncated
to 71 characters.
This has been corrected.

Meta Entity: call of a Data Element defined more
than once in the network if its format is the same
(C:030347)
The description of a Meta Entity can call a Data
Element defined more than once in the Libraries network
if its format is always identical in these various
Libraries.
In this case, the 8488E error message will no longer be
displayed.
Note:
The preprocessor has been modified. The user programs
processing with the CMEDEL and EMEDEL tables must be
regenerated and reprocessed.

UPDT: Printing and recycling grouped transactions
(C:030358)

UPDT: Printing and recycling grouped transactions.

Some transactions of the MB file in input of the UPDT
procedure are grouped in order to obtain an update
transaction in the MV file.

The update output report now print the whole transactions
in input.
In case of error on a group transaction, its elements are
written in the recycled transactions file.

UPDT: Management of update transactions on
Data Elements
(C:030359)
Now updating only one of the three formats of a Data
Element is possible via the UPDT procedure.
In the identification line, the user must not indicate an
'N' in column 67.

UTM2 will create the new Relation in the
Library in which a Meta Entity uses it
(C:030360)
UTM2 will create the new Relation in the Library in which
a Meta Entity uses it.

The error 6157 ('THE ENTITY CODE MUST NOT
CONTAIN BLANKS') is changed into a warning
(C:030363)
The error 6157 is now changed into a warning and the message
is:
'THE ENTITY CODE CONTAINS BLANKS'.

VINS: Installation of Methodologies. The procedure
will list the entities to be purged (REOR)
(C:030381)
VINS: Installation of Methodologies. The procedure
will list the entities to be purged (REOR)
The VINS procedure can be used to install the Methodology
entities and their relations in session 1 and in
inter-library. If these entities already exist in the
Database somewhere else than in inter-library, there will
now be loaded into the PAC7RM file and will then be able to
be purged by the reorganization procedure.

PACS: The 'procedure function code' of the *
line is now controlled
(C:030395)
PACS: The 'procedure function code' of the *
line is now controlled
If the procedure function code of the * line (position
29 on 4 characters) is not:
MLIB, SAVE, SASN or UXSR,
the error 9136 'Unknown procedure' is sent and the
procedure no longer ends with an I-O error on the
AR file.

ACTI: the session number in the statistics screen
is now displayed on 5 characters
(C:030410)
Actually, the number appeared in an 8-char internal format.

UPDT on extension or client UE: the Descriptions
were wrongly converted into uppercase
(C:030504)
UPDT: Now this procedure takes into account the value of the
'Uppercase' field of the Meta Entity.

'No lock extraction' option in EXLI with
CPSN format
(C:030509)
'No lock extraction' option in EXLI with CPSN format

In EXLI with the CPSN format, the update transactions for
entity locks were generated, even if the '*' line
contained the 'No lock extraction' option.
This has been corrected.

The reorganization procedure (REOR) filters
erroneous data
(C:030522)
If the session number of a record is greater than the
current session number, this record is not taken into
account.
It will appear in the report of step PTU200, with the
following error message: INVALID SESSION.

Partially updating an Input Aid call used to
wrongly reset the other fields to blank.
(C:030558)
In batch mode, updating some of the fields of an Input Aid
call used to reset to blank all the other fields of this
Input Aid.
This has been corrected.

VINS: Update of the methodology Meta Entities in
inter-library mode
(C:030560)
VINS: Update of the methodology Meta Entities in
inter-library mode. (for Microfocus or Acucobol environment)
Updating Meta Entities in inter-Library mode is now
possible even if these Meta Entities already exist in a
lower-level Library.

The deletion in batch mode of a User Entity with
the YxxDEF table is correctly operated
(C:030573)
The deletion in batch mode of a User Entity with the
YxxDEF table is correctly operated.

PACX-EXPJ: "old' transactions not printed if
they are not part of the input selection
(C:030602)
PACX-EXPJ: the 'old' transactions are not printed if they
are not part of the input selection.
The 'old' transactions issued of PJ25 are printed only if
they are part of the selection specified in the input card
of the EXPJ procedure.

RMEN: When an entity with a -CR is moved up,
the code of the linked UE is recognized
(C:030606)
When an entity with a -CR is moved up, the code of the
linked User Entity is no longer ignored.

Wrong display if batch update of a -Gx line on a
line which called an Input Aid. Corrected
(C:030619)
When -Gx lines were updated in batch mode, if a line which
called an Aid Input was replaced by a simple line,
the Input Aid was wrongly displayed with the contents of the
simple line as its parameters.
This has been corrected.

ACTI: the parameters' labels are correctly
returned in the prints
(C:030642)
In the Analysis of Activity module (ACTI procedure), the
values associated with the parameters are now returned
with the correct label instead of the internal code.

EXLI: incomplete extraction of a label if it
exceeds 66 char and then contains + than 66 blanks
(C:030655)
EXLI: incomplete extraction of a label if it exceeds
66 characters and then contains more than 66 blanks.
A label can contain up to 256 characters.
When it is extracted, it can be divided into four
66-character records. If the label is interspersed with
blanks, one of these records can be constituted of a totally
blank label. This record is inserted between records whose
labels are not blank. However it must not be ignored and
must be passed on to the extraction file.
This is corrected.

GY30: Retrieve the length of the contents of User
entities for transactions output from EXPJ
(C:030726)
GY30: retrieve the correct length for the contents
of User entities issued from EXPJ transactions.
The correct length is retrieved with the access to the
Meta-entity description.
The contents of the Definition and Descriptions of the
User Entities are now correctly retrieved.

History of Generation Environments:
deletion of obsolete lines
(C:030785)
Modification of the EXPU procedure:

In the search criterion of the frozen sessions to be purged,
the external name of the entity must be recognized.
A UPDT (P) output is proposed to delete the obsolete LEG
records (YC1) which are in production.

CPSN/UPDT: one field of the lock in the MB file
is not filled in if the entity is not a UE
(C:030888)
CPSN/UPDT: one field of the lock in the MB file
is no longer filled in if the entity is not a UE
The lock record does not need the B1 technical field.
The Entity Code field (ex: C for Data Element, 0 for
Program...) is enough for the correct update of an entity
other than a User Entity.

Updating a User Entity whose code contained a
blank used to cause an ABEND (UPDT)
(C:030907)
It is now possible to create a User Entity containing one
or more blanks in its code via UPDT.

Purge of the history of the entities put in
production
(C:030928)
Purge of the history of the entities put in production
The parameter in column 26 represents the number of lines
of the production turnover history, whatever the session
number.

EXTR: the code of the user entity called by
relation appears in the extraction stream
(C:030949)
EXTR: the code of the user entity called by relation appears
in the extraction stream.
The transactions file output of the extraction now contains
the code of the user entity linked by relation (-cr).

REOR: created deletion index
(C:031083)

In the meta entity description, it is possible to remove the
use of a relation (set to blank).
In that case, the linking indexes of this relation
are correctly removed by the REOR procedure.

HIPM: the assignment of the 'PAC7UR' file has been
added (Unix and Windows repositories)
(C:031168)
HIPM: the assignment of the 'PAC7UR' file has been
added (Unix and Windows repositories)
This work file was not assigned and this caused an abend
in the first step of the procedure.
This has been corrected.

RMEN: the return code of the 'Non-existing called
entity' error is now 4
(C:031210)
RMEN: the return code of the 'Non-existing called
entity' error is now 4.

Retrieve

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.

UTM2: a step to check the ME file issued from
UTM1 has been added
(C:029926)
UTM2: a step to check the ME file issued from UTM1 has
been added.
The ME file issued from the UTM1 procedure contains the list
of relation calls. Each relation must be linked to only one
entity type.
To guarantee the validity of this file, a control program
(ptume3) is added in the UTM2 procedure.
If several entity types are linked to a same relation, a
display is sent requesting the correction and the
re-execution of UTM2.

MB25: the insignificant '&' are taken into
account in the comments retrieval
(C:030047)
MB25: the insignificant '&' are taken into account in the
comment retrieval.
The 'V3' comment lines were incorrectly formatted and the
type of line was '&'.
This has been corrected.

MB25: management of Data Elements' continuation
lines
(C:030051)
MB25: Errors in the management of Data Elements'
continuation lines cause rejects in UPDT
If a transaction concerning the internal format of a created
Data Element is followed by a transaction concerning
the same Data Element and the same format, this format is
wrongly considered as the continuation of the first one.
Example of MB file output by MB25:
Format Continuation char. Continuation char
before correction after correction
CCELEM I + blank
MCELEM I ++ +
MCELEM E ++ ++
MCELEM S blank blank
Second case:
CCELEM I + blank
MCELEM I ++ +
MCELEM E ++ *
MCELEM I ++ +
MCELEM S blank blank

UTM2: the label of the old relation is retrieved
in case of transformation into new relation
(C:030080)
UTM2: If an old relation is changed into a new relation,
its label is kept.

UTM1: limitation of the -CR extraction to the
processed relation
(C:030111)
UTM1/UTM2: limitation of the -CR extraction to the processed
relation.
When an entity called, for a same line number, different
relations in different sessions, UTM1 wrongly extracted, for
each relation, all the records (-CR) corresponding to this
line number, including data that concerned other relation
codes.
The extraction is now limited to the processes relation.

PE25: the list of the authorized procedures
has been updated
(C:030165)
PE25: the list of the authorized procedures for a minimum
profile has been updated (pbmin).
The ARAD, SVAD, RSAD, and ROAD procedures are no more part
of the authorized procedures for this profile.

Optimization of the PJ25 and UV25 retrieval
procedures
(C:030209)
Optimization of the 2.5 -> 3.5 retrieval procedures:
- of the PJ file (BVPPJ25 procedure) by limiting the
accesses to the AE file
- of the UV file (BVPUV25 procedure) by limiting the
accesses to the AE file and deletion of the loop if the maxi
key is missing in the 2.5 UV file.

PG25: The addition of before/after cards on the
GCD command description is taken into account
(C:030214)
PG25: The addition of before/after cards on the description
of the GCD command is taken into account.
The before/after cards fields of a GCD command issued from
the 2.5 version are set to blank.

PC25: Reinitialization of the Input Aid type
(C:030335)

PC25: Reinitialization of the Input Aid type.
The Input Aid type is found on the description. It is
reinitialized each time a new Input Aid is processed.
When this type was not specified (set to blank) on the
description and when the first description line was a
comment line, the Input Aid type was that of the previous
Input Aid.
This has been corrected.

UTM2 will create the new Relation in the
Library in which a Meta Entity uses it
(C:030360)
UTM2 will create the new Relation in the Library in which
a Meta Entity uses it.

After PC25 retrieval, the descriptions of
Meta Entities can be aligned
(C:030375)
After the retrieval, the description of a Meta Entity,
defined in various Libraries, can be aligned.
A Meta Entity will be chosen as the reference (master).
The same Meta Entity (target), which exists in another
network, can be modified in order to be the image of the
master Meta Entity.
The internal identifiers of the Data Elements which are
common to the master and the target will be aligned.
Only modifications will be performed: if the target
description is more complete, it will remain as
such.
If Data Elements of the master Meta Entity are not called in
the target Meta Entity, the descriptions of the target
will not be completed.
The User Entities of the modified target Meta Entity will
also be modified.
You must perform the following operations:
- Save the Database
- Extract the master Meta Entity via EXTR with the
CPSN format
- Modify the target Meta Entity and its UE via Vins.
In the VINS user input, you must indicate:
. the Library of the target Meta Entity
. 'F' in column 33

UTM2: the relations are now created in the H
session which is the closest to its use in entity
(C:030387)
UTM2 will create the new Relation in the same session as
that of its use in an entity (c30360 follow-up).

UTM2: The error '9006' is no longer displayed
when it applies to a Relation
(C:030505)
UTM2: During the update, the error '9006' (creation of
a record which already exists) is no longer displayed if
the entity of the record is a Relation.
These existing records are not updated but no error message
is sent.

GY30: Retrieve the length of the contents of User
entities for transactions output from EXPJ
(C:030726)
GY30: retrieve the correct length for the contents
of User entities issued from EXPJ transactions.
The correct length is retrieved with the access to the
Meta-entity description.
The contents of the Definition and Descriptions of the
User Entities are now correctly retrieved.

Retrieval of Development Database: Modification
of Block Description lines
(C:030752)
In the Generation Elements (-GG) lines, the following line
types can be entered: G, P, V and Z.
In the case of an Additional Description on a Data Element,
<elem > in the 'Description' field of the line, the
previous values are not changed. All the values except
those of the list will be replaced with '*'.
All these lines will be correctly retrieved in the
-GG description.

PC25-input aids: the type of comment lines in
descriptions is taken into account
(C:031003)
PC25-input aids: if the type of comment lines in
descriptions is filled in, it takes part in the input aid
determination and in the assignment of its calls in -Gx.
From now on, a comment line type that is filled in is
not ignored anymore .

Rename and move utility

RMEN: When an entity with a -CR is moved up,
the code of the linked UE is recognized
(C:030606)
When an entity with a -CR is moved up, the code of the
linked User Entity is no longer ignored.

Software Config. Management

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.

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.

SCM: The number of generation commands processed
in the same run is now extended to 9999
(C:030367)
SCM: A crash occurred when the number of generation commands
exceeded 1000 in the same run. This number is now extended
to 9999.

History of Generation Environments:
deletion of obsolete lines
(C:030785)
Modification of the EXPU procedure:

In the search criterion of the frozen sessions to be purged,
the external name of the entity must be recognized.
A UPDT (P) output is proposed to delete the obsolete LEG
records (YC1) which are in production.

Purge of the history of the entities put in
production
(C:030928)
Purge of the history of the entities put in production
The parameter in column 26 represents the number of lines
of the production turnover history, whatever the session
number.

HIPM: the assignment of the 'PAC7UR' file has been
added (Unix and Windows repositories)
(C:031168)
HIPM: the assignment of the 'PAC7UR' file has been
added (Unix and Windows repositories)
This work file was not assigned and this caused an abend
in the first step of the procedure.
This has been corrected.

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.

The .S choice on an -XP screen in Z1 view
stopped on the first line found
(C:030318)
The .S choice on an -XP screen in Z1 view
stopped on the first line found.
The problem came from the fact that the search was not
performed on the -XP lines of a library sub-network.
This is now corrected.

Security Systems Interface

Generation with database under RACF control: the
USER=xxx,PASSWORD line is no more generated
(C:030974)
When a generation is launched, if the VA Pacbase database is
under RACF control, there is no more 'USER=xxx,PASSWORD'
line in the header of the generated flow.

Sub-network Comparison Utility

EXTR-CPSN: replacement of a comment line with an
Input Aid call line
(C:029930)
EXTR-CPSN: replacement of a comment line with an
Input Aid call line
If, in a library network, the -G is an Input Aid call and in
the second library network a comment line, the transaction
is deleted in the slave network before the transaction is
created in the master network.
This is 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.

'No lock extraction' option in EXLI with
CPSN format
(C:030509)
'No lock extraction' option in EXLI with CPSN format

In EXLI with the CPSN format, the update transactions for
entity locks were generated, even if the '*' line
contained the 'No lock extraction' option.
This has been corrected.

SASN: The Libraries hierarchy of the Database
is kept
(C:030622)
SASN: The Libraries hierarchy of the Database
is kept
The Libraries created by SASN are now created with the
correct hierarchy.

EXLI: incomplete extraction of a label if it
exceeds 66 char and then contains + than 66 blanks
(C:030655)
EXLI: incomplete extraction of a label if it exceeds
66 characters and then contains more than 66 blanks.
A label can contain up to 256 characters.
When it is extracted, it can be divided into four
66-character records. If the label is interspersed with
blanks, one of these records can be constituted of a totally
blank label. This record is inserted between records whose
labels are not blank. However it must not be ignored and
must be passed on to the extraction file.
This is corrected.

CPSN/UPDT: one field of the lock in the MB file
is not filled in if the entity is not a UE
(C:030888)
CPSN/UPDT: one field of the lock in the MB file
is no longer filled in if the entity is not a UE
The lock record does not need the B1 technical field.
The Entity Code field (ex: C for Data Element, 0 for
Program...) is enough for the correct update of an entity
other than a User Entity.

SQL Language

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.

Blocks: The action code could wrongly be entered
on an Input Aid call line
(C:029921)
Blocks: The action code on an Input Aid call line coming
from a higher-level library in the -GG can no longer be
entered.
An Input Aid call line from a higher-level library in a
Database Block -GG (1st of 2nd level) did not display
a dot in the 'Action code' column. Hence an action code
could be entered, but with an error message.
This has been corrected.

DBD: NOT NULL WITH DEFAULT does no more contain
the initial values if the CONT column is set to S
(C:030714)
DBD : NOT NULL WITH DEFAULT does not contain anymore the
values of the VALUE/SFC column if the CONT column is set to
'S'.

Erroneous control cards in front/back
and generation of SQL Blocks
(C:030735)
Erroneous control cards in front/back
and generation of SQL Blocks
An unknown control card in front of flow no longer inhibits
the generation of the next Blocks in the flow of requests.
In some cases, an unknown control card in front of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
In all cases, an unknown control card in back of Block
no longer inhibits the generation of the next Blocks in the
flow of requests.
A generation request without any control card in front/back
no longer inherits the control cards in front/back of the
preceding request.

Generation of Oracle database block: the clause
NOT NULL WITH DEFAULT is no more generated
(C:030815)
The clause NOT NULL WITH DEFAULT is no more generated for
the ORACLE database blocks.
And, the value to be checked is not taken into account for
any block type.

SQL/SERVER generation: the initial value for
NOT NULL DEFAULT depends on the column type
(C:030820)
Generation of SQL SERVER Database Blocks:
The initial value to be entered for NOT NULL DEFAULT now
varies according to the column type.

10*R FF00: if the access type is not indicated,
all the access functions to FF00 are replaced
(C:030914)
On-Line Systems Development generator:
F80 10*R FF00: if the access type is not indicated, all the
access functions to FF00 are now replaced.

Business Component and Oracle: a date present in
the WHERE clause is complemented with TO_DATE.
(C:031257)
In a Business Component which accesses an Oracle Database,
the date-formatted fields present in the WHERE clause are
complemented with TO_DATE.

Pac/Impact

IPFQ: the PAC7IL report of BVPAN220 was in English
for a French installation
(C:030508)
The PAC7IL report is now always edited in the correct
language.

Text

CH: T......D: positioning marks on I- and J-type
lines
(C:030390)
In character mode, the I- and J-type lines which are used to
assign text lines to the documentation of entities include
positioning marks for entering the entity codes to which
text lines will be assigned.

Assignment of Text lines: The User Entities whose
identifier is 6 char. long max. may not exist
(C:030399)
Assigning Text lines to a User Entity which does not
exist is now possible if the identifier of this User
Entity is 6 characters long maximum.

Miscellaneous : Online

The Database to be restored is indicated
in on-line mode
(C:029011)
If the message 'Database to restore' is displayed, the
(Administration or Development) Database to be restored
is indicated in on-line mode.

A new description of a Meta-Entity can be
created (in character mode)
(C:029282)
A new description of a Meta-Entity can be created, even
if this Meta-Entity is used.

Now a description of a Meta-Entity can be created or
modified in online mode if none of the User Entities
related to this Meta-Entity contains a line of this
description.
Until now, as soon as a User Entity was created from the
Meta-Entity, a control used to inhibit the creation of a
new description on this Meta-Entity.
This control has been refined.

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 converted
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 'documentation, help, generation and options' because
'Gx' is sub-divided into GC, GE, GG, GO.

The 'M' and 'T' action codes will no longer
delete the unchanged values of Input Aids
(C:029822)
The 'M' and 'T' action codes will no longer
delete the unchanged values of Input Aids

It is possible to consult and update meta
entities in online mode
(C:029830)
It is now possible to consult and update meta entities
in online mode.

LL screen: The choice -l.... no longer truncates
the user code
(C:029858)
LL screen: The user code is no longer truncated in the
screen obtained via the choice -l.....

Blocks: The action code could wrongly be entered
on an Input Aid call line
(C:029921)
Blocks: The action code on an Input Aid call line coming
from a higher-level library in the -GG can no longer be
entered.
An Input Aid call line from a higher-level library in a
Database Block -GG (1st of 2nd level) did not display
a dot in the 'Action code' column. Hence an action code
could be entered, but with an error message.
This has been corrected.

User entities: warning if areas cannot be
displayed in online mode
(C:030082)
When the description of user entities is displayed in online
mode, if the remaining place on the line is not enough to
completely display the following data, a warning is
displayed.

PF11 branching on a database block description
and on a segment
(C:030109)
For the database blocks and segments, the PF11 function key
allows to branch on the generation elements.

Block -DR: updating an I- or J-type line
deletes the -DRnnnK
(C:030203)
Block -DR: updating an I- or J-type line
deletes the -DRnnnK.

Let us consider an I-type line (numbered nnn) on a
Relational Block description (-DR) in which you have entered
the key's Data Elements (-DRnnnK). (Note that a + is
displayed at the end of the line).
If you modify this line (ex: is you enter 'U' in the
'Key Type' column), the key's Data Elements are no longer
deleted (Note that the + is still displayed).

Meta Entity: call of a Data Element defined more
than once in the network if its format is the same
(C:030347)
The description of a Meta Entity can call a Data
Element defined more than once in the Libraries network
if its format is always identical in these various
Libraries.
In this case, the 8488E error message will no longer be
displayed.
Note:
The preprocessor has been modified. The user programs
processing with the CMEDEL and EMEDEL tables must be
regenerated and reprocessed.

B......GN...: The SQL return code is not displayed
after a request for a catalog updating.
(C:030383)
B......GN...: The SQL return code is not displayed
after a request for a catalog updating.
This has been corrected.

CH: T......D: positioning marks on I- and J-type
lines
(C:030390)
In character mode, the I- and J-type lines which are used to
assign text lines to the documentation of entities include
positioning marks for entering the entity codes to which
text lines will be assigned.

Correct deletion of an old UE which contains a
Data Element (x(6) format) linked to a Segment
(C:030408)
An old UE which contains a Data Element (x(6) format)
linked to a Segment via a Relation can now be
deleted without any problem.
This change also applies to the Data Elements linked
to Reports or Data Structures.

For Programs written in lines 8, the long
conditions are managed correctly
(C:030426)
For Programs written in lines 8, the long
conditions are managed correctly.
In the lines '8' where the condition is written on more than
32 characters, the 3 characters which are not displayed are
not reset to blank.

'Devirtualizing' a Library with/without renaming
no longer causes the message 'Unknown Lib. code'
(C:030488)
'Devirtualizing' a Library with/without renaming
no longer causes the message:
'UNKNOW LIBRARY CODE'

Report layout: the modification of label number or
jump code is correctly journalized
(C:030541)
Report layout: the modification of label number or jump code
is correctly journalized.
If a line is modified at label number level or jump code
level but without modification in the content of the line
and if the visualization window begins with a value
different from 1, 67, 133 and 199, the journalization
transaction is associated with the first part of the label.

Screen simulation: the columns are respected
on all platforms
(C:030604)
The screen elements are correctly displayed upon a
simulation (-SIM choice). There is no longer a one-character
shift.

An existence check of the EU Definition is no
longer performed upon the deletion of its lock
(C:030605)
Now an existence check of the User Entity Definition
is no longer performed upon the deletion of its lock.
The deletion must be performed on the line where it is
displayed.

Update of long data in two contexts
(C:030665)

Update of long data in two contexts

'Long' data is data which cannot fit into a physical
record of the AR file.
This applies to:
- User Entities (Definition or Description)
- All the -Gx type Descriptions which include a call to
an Input Aid
- The description of Report labels

The creation of this data in a session no longer impacts the
images of this data in another context.

The short code of a deleted elementary component
can be re-used
(C:030733)
A user entity can have a 'short code' field in its
description.
In that use case, the creation of a user entity, after
its deletion, but changing the short code is correctly
performed.
This is true whatever the entity type (client or extension),
in particular for the eBusiness model entities.
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).

DBD: wrong paging on the input screen of
Index keys (B......DR...K)
(C:030742)
DBD: wrong paging on the input screen of
Index keys (B......DR...K)
If the keys of an index, whose constituting Data Elements
are contained on more than one screen page, are updated,
the screen is refreshed after the update.
There is no more a wrong paging of the continuation screen.

Warning upon the creation of a UE already
present in a lower-level library
(C:030834)
When creating a User Entity already present in a lower-level
library, the following message was not displayed:
'ENTITY TO BE CREATED BUT ALREADY EXISTING IN A SUB-LIBRARY'
This is now corrected.

LCS with view U1: the DS name from the
higher-level library is displayed
(C:030842)
LCS with view U1:
If the Data Structure is not defined in the current
library, the name of this Structure in the higher-level
library is displayed.

Input of User Entities: protection against
Low-Values
(C:030892)
The low-values resulting from the 'End-of-Field deletion'
and 'Character deletion' will be replaced with blanks.

Use of a Relation: the screen correctly displays
the User Entities
(C:030905)
Use of a Relation: the screen correctly displays
the User Entities

The access to a Database which session number is
greater than 9990 is forbidden
(C:031028)
To avoid a reset to 0 of the Database session number once
it has reached 9999 and to allow time to the Database
Administrator for a backup execution, before that of the
Session Compression Utility, the Database automatically
locks when its session number reaches 9990.

Upload / Download

Improved management of technical locks
(C:029857)

Technical lock on a Screen Description:
- This lock is visible on the Definition,
- Another user can modify the Definition but also all the
Descriptions which are not locked.
- A message is displayed if the Description is locked.

Entity Lock

Creation of locks in batch update
(C:029226)

The request for the creation of locks is no longer rejected.

Improved management of technical locks
(C:029857)

Technical lock on a Screen Description:
- This lock is visible on the Definition,
- Another user can modify the Definition but also all the
Descriptions which are not locked.
- A message is displayed if the Description is locked.

LL screen: The choice -l.... no longer truncates
the user code
(C:029858)
LL screen: The user code is no longer truncated in the
screen obtained via the choice -l.....

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.

Error message changed if a lock is requested on a
Data Structure while a Segment is already locked
(C:030118)
If a lock is requested on a DS while a Segment of this DS
is locked, the following message is displayed:
LOCK IMPOSSIBLE: DEPENDENT ENTITY LOCKED BY xxxxxxxx
----> The AE file is to be retrieved.

An entity can be locked, even if this lock exists
in a lower-level lib. and if the lib. is protected
(C:030813)
Now it is possible to lock an entity whose library includes
a 'Protection of Extraction Entities', even if the locked
record exists in a lower-level library.

The documentation of LL screen no longer mentions
the fields removed since version 2.5
(C:030944)
The documentation of the 'LL' screen no longer mentions
the fields removed since the version 2.5 (ST, L and X).


Rate this page:

(0 users)Average rating

Document information


More support for:

VisualAge Pacbase
VisualAge Pacbase Server

Software version:

3.5

Operating system(s):

Windows 2000, Windows NT, Windows XP

Reference #:

1313120

Modified date:

2011-01-29

Translate my page

Machine Translation

Content navigation