ca.portal.admin

DAR voting

Discussion created by ca.portal.admin on Nov 2, 2005
Hi everyone,

The IUA & Computer Associates need your help. CA is busy working
working on the next release of CA-IDMS, and would like your feedback on
the DARs and Suggestions that were submitted to CA.

The IUA went thru the list, and have posted the 28 highest ranking ones
on our website. We would like you to give us your feedback on these
DARs/Suggestions. Please visit www.iuassn.org. Once you've signed on,
if you're a paid member of the IUA, you can get to the DAR Ballot page
off the MEMBERs ONLY section.

Please vote by November 11th 2005, as the results will be reported back
to CA during CA-World, which is being help in Las Vegas, from November
13th to the 17th 2005.

Thank you,
Laura Rochon
IUA
This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipients of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Third Party Vendors for TCP/IP IDMS Access
"I would like to pose a question to members of the list.

Our applications folks are contemplating getting a third party product for
TCP/IP access to IDMS-DC systems instead of developing such applications in
house. The ""buy vs. build"" question might make sense if the economics are
right and the products work reasonably well.

I would like to hear from folks who are using such products to get a sense
of the technical feasibility issues.

TIA

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
DAR voting
"Hi everyone,

The IUA & Computer Associates need your help. CA is busy working
working on the next release of CA-IDMS, and would like your feedback on
the DARs and Suggestions that were submitted to CA.

The IUA went thru the list, and have posted the 28 highest ranking ones
on our website. We would like you to give us your feedback on these
DARs/Suggestions. Please visit www.iuassn.org. Once you've signed on,
if you're a paid member of the IUA, you can get to the DAR Ballot page
off the MEMBERs ONLY section.

Please vote by November 11th 2005, as the results will be reported back
to CA during CA-World, which is being help in Las Vegas, from November
13th to the 17th 2005.

Thank you,
Laura Rochon
IUA

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
BIUA IDMS usergroup event Decmber 8th
"The Benelux IDMS User group Association will give a user event on
Thursday, December 8th at the BELGACOM offices in Brussels


Preliminary agenda:

Advantage CA-IDMS Status and Plans.
Express Reorg and a Glimpse into the Future.
(J-P Defeyter, CA-IDMS Development Brussels)


DARS Overview and User Experience.
A Synchronisation method.

(Pete Charles, Cogito)

TCP/IP and CA-server review in r16.

(Guy Derkinderen, CA-IDMS Development Brussels)


Integration and synchronistion

(Dan Finerty, Neon Systems)


So pinpoint your agenda

Jan Rabaut Luc Denaeyer
Chairman BIUA Co-Chairman BIUA







--------------------------------------
Dexia Bank disclaimer :
http://www.dexia.be/maildisclaimer.htm
--------------------------------------




"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DAR voting
"I know you're busy.....any status on the BOD voting on the website?

Bob Wiklund
Tiburon Technologies
wiklund@tiburontech.com
623 594-6022

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
List of DARs/Suggestions on Ballot
"Hi all,

For all you IDMSLer who are not a paid member of the IUA, here is the
list of DARs/Suggestions that are currently on the DAR ballot. If you
are a member of the IUA, please visit the IUA website at www.iuassn.org.
After you login, check out the Dar ballot under the Members only
section and give us your opinion on these DARs/Suggestions.


#1 Web Services to send/receive HTLM, etc. using IDD
Now that there is a TCP/IP interface for IDMS, we would like to see a
web server similar to the functionality provided in CICS. This web
server should provide an API to receive/send HTML from ADS and COBOL. It
would also be nice if entities such as graphic files and HTML templates
could be stored in the IDD.

#2 Reload Locks Entire Segment
In ref. to APAR LO37050, UNLOAD-RELOAD utilities lock all areas included
in an SQL segment but would be better if only the affected areas are locked.

#3.SQL Create Index Symbolics
Non-SQL DDL separates the logical and physical specifications for
indexes by means of SYMBOLICS. SQL DML however does not have this
separation, i.e. the CREATE INDEX syntax does not provide the option to
use such SYMBOLICS. Non-SQL: CREATE INDEX ... SYMBOLIC INDEX ... SQL
: CREATE INDEX .... <physical characteristics of index>
This causes a problem when having multiple SQL databases sharing the
same logical structure, but having different physical sizes. Because the
INDEX SQL DDL statement does not allow the usage of SYMBOLICS, they need
to define separate/different SQL database definitions. The existance of
these symbolics for SQL is important, if users have the intention of
defining such SQL databases (several databases with the same logical
structure, but different sizes).

#4 Look Doesn't Show Index Symbol
IDMSLOOK reports for DMCL and SUBSCHEMA do not show all SYMBOLIC types.
The DMCL report shows the primary pagerange symbolic but not other types
such as INDEX symbolics.

#5 Prefetch Enhancement Request
Product FAST ACCESS does look-ahead reads at the Cylinder level.
Enhance PREFETCH to do Cylinder level EXCPs.

#6 Want To See History
It would be useful for this product to show history of space
utilization. This is essential to monitor the need for expansion and to
predict usage requirements.

#7 Statistics field values DECREA
It would be useful if the size of the system statistics fields be
increased to doublewords for all fields in DCMT D STAT SYSTEM display.
This is necessary because they will soon will be a 24X7 shop and will
not re-cycle CVs for long periods of time. A recent test, CV was up
from 12/19/04 until 1/19/05 and Total SYS time was reset to 00 after
excedding 99 hours and DATABASE calls counted down after hitting
2,100,000,000.

#8 SIGNON to
IDD

Within VisualDBA there is no way to set the usage-mode for IDD. The
default usage-mode of our IDD implementation is retrieval, set by SYSGEN
IDD statement to avoid deadlocks.

#9 CALC REDEFINES not handled in
QuickBridge
If a CALC key contains ""Redefines"" QB will not be able to use that CALC
key The problem is that QB does not understand structures with
""redefines"", so it cannot clearly determine the key when it gets the
elementary items of the CALC key. The result is that whenever the
calckey contains a ""redefines"", the table procedure program generated by
QB will not contain a path for calc access to the record.

#10 Reading SQL table with KEYFILE
15.0/Customer requests to add following functionality in CULPRIT :
they want to use SQL requests in CULPRIT together with the KEYFILE
option, i.e the SQL SELECTs with a WHERE clause, where the variables to
be used in the WHERE clause should be taken from a KEYFILE. This is
currently possible for nonsql requests and ASF table requests. Customer
would like this functionality been extended to SQL requests as
well.

#11 Make VISUAL DBA Easier to use
Visual DBA allows you to do many activities but it requires you to use
DCUF and DCMT commands to do these activities/tasks. Routine tasks that
a DBA is required to do should be able to be done by clicking a button -
to cancel a task, delete a user who is unable to signon because they are
already signed

#12 INDEX with UPLOW Characters
Need to setup an INDEX on an SQL TABLE where the involved column is an
alphabetic field. Data for this column can be entered in upper & lower
case, which would influence the order of the index. How to avoid this,
i.e. make sure that every value to be stored in upper case F.e. in
ORACLE, the option exists to use (UPPER(column)) in the definition of
the INDEX. How to do this with IDMS SQL ? As example, the ORACLE
syntax looks like : CREATE INDEX idx_case_ins ON
my_table(UPPER(empname)); ***** As a result, the keyvalue is ALWAYS
added in the index in upper case, despite of the way it has been
entered. Depending on the SELECT, ORACLE only accesses the index
structure, or also needs to read the table rows.

#13 Extended VIB Statistics
Under Release 10.2 code was added to provide extended VIB statistics
which actually contained statistics related to indexing. Documentation
for this feature was omitted for later releases of IDMS and the required
dictionary record for the extended statistics was never supplied to the
user base. However the code to return these numbers still exists and
works as of Release 15.0

#14 DBAN and Wrong CALC Chains
IDMSDBAN attempts to identify when a CALC record is connected to the
wrong CALC chain occurrence based on its calckey by hashing the calckey
and then placing the dbkey of the calculated target page's SR1 into the
intermediate record as the set's owner. By doing this the record will
in essence be removed from chain in which it is connected generating
error messages showing bad NEXT and PRIOR pointers. In addition it may
also display a line stating that a set was found without an owner
pointer depending on the intermediate records created by DBN1 and/or the
sequence in which DBN2 encounters the intermediate records during the
first pass. If a user is aware that calckeys may have been compromised
or that a record is attached to an incorrect occurrences of the CALC set
this information is certainly usable towards correcting the database.
However when just approaching the various error messages as broken
chains it can be very confusing and difficult to determine that the
problem is a record connected to the wrong CALC set occurrence since
examination of the database (via a PRINT PAGE) may show no broken sets.
In addition users can also be misled when a page that seems
unrelated to the broken set is listed as a result of the usage of the
correct target page's SR1 dbkey in the problem record's intermediate
record as the set owner. The user would like to see IDMSDBAN modified
to provide a more explicit indication that a given CALC record is
connected to the wrong CALC set occurrence with an indication of the
true target page more clearly specified to avoid trying to determine
what or if some other broken chain also exists on that page.

#15 Produce Dump By Program
Client desires the ability to produce a snap dump 'dynamically' by
dialog name or program name. Similar to the process that is used in MVS
for a SLIP trap dump. This would include the ability to turn on Snaps
for a single program or even a time interval, that would automatically
vary off after a dump/snap is produced.

#16 BLOB Support for IDMS
RecordsSupport of BLOB (Binary Large Objects), such as pictures,
documents etc in CA-IDMS

#17 TCP/IP Support in BS2000
Make CA-IDMS TCP/IP functionality also available for the BS2000
operating system

#18 Capability Of Deleting All on Maps
The batch mapping compiler RHDCMAP1 fails with DC384108 MODIFY OR DELETE
OF MAP NOT ALLOWED. Map is checked out by MAPC if any of the maps being
compiled is checked out in MAPC. Likewise ADSOBCOM fails with DC497042
Dialog is checked out to ADSC and cannot be compiled in batch. Client
would like the capability to delete check outs for maps and dialogs in
groups using masking as oppose to deleting them
individually.


#19 COMP-5 Support
IDMS does not currently support the Computational-5 usage mode for
elements defined in the dictionary with IDD or IDMSDDDL. Please add
support for this usage mode.

#20 OLP to Exclude SELECTIVE MSGS
Currently with OLP, you can issue command NOMESSAGS or NODUMPS. Would
like a DAR to allow OLP to exclude 'only' specific message(s). For
example NOMESSAGE DC999999 or DC9*, it would also be benificial to be
able to exclude mutiple messages, via a list function of some kind.

#21 SQL Assistant - Unusable Table List
Using the ""Command Console"", ""SQL Assistant"" and the ""Select"" option,
the retrieved list of entities in the 4 windows (Tables / Views / Table
Procedures / Non SQL Tables) are all sorted on table-name instead of
schema and table-name. This makes it very difficult to navigate thru
that list. The client requests some option (e.g. check-box with
radio-buttons, ...) to sort the list(s) on both schema- & table-name or
only on table-name. Using the ""Command Console"", ""SQL Assistant"" and
the ""Select"" option, the retrieved list of entities in the 4 windows
(Tables / Views / Table Procedures / Non SQL Tables) are all sorted on
table-name instead of schema- and table-name. This makes it very
difficult to navigate thru that list. The client requests some option
(e.g. check-box with radio-buttons, ...) to sort the list(s) on both
schema- & table-name or only on table-name.

#22 SQL use of AUTO-BULK
Require AUTO-BULK support to SQL option.

#23 GROUP BY an Expression
Client would like to have the functionality where the argument of the
GROUP BY clause can be an expression rather than being limited to one or
more column names as is the case today. e.g. SELECT A+B, SUM(C) FROM
T1 GROUP BY A+B;

#24 New Minor Code Returned for Limits Violation
Add new minor code to be returned to programs when it is abended because
it has exceeded limits. This will enable programs to detect when they
have been terminated due to an exceeded limit proceed accordingly. This
would be in addition to the DC244003 already issued to the DC log.
(please note issue suggested use of exit 20 to achieve this. This was
tried but did not work as required).

#25 New SQL Syntax for Header/Detail Processing
Require a different syntax in the SQL SELECT statement where one way
would write the header and the SQL statement and the other way would
just write the detail lines. With that special syntax, the programmer
would choose what way to go. Choosing to write only the detail lines
would allow someone to submit an SQL query and create output that could
easily be loaded into a flat file.

#26 Map Regeneration to warn Affected Dialogs
When a non-critical map is migrated, regenerated the affected dialogs
instead of generating a warning message. When a non-critical change is
made to a map, dialogs using that map do not need to be regenerated in
the source dictionary. However, when that map is migrated, the changes
are not made in a modify fashion, the map on the target system is
deleted and re-added from punched source. If the migration is
change-only as it typically is to prevent migrating a lot of unchanged
entities, the dialog will not be regenerated on the target system and
instead a VALD230W (I think) message is issued which can lead you to
think the dialog will be regenerated. A new-copy statement is also
generated but without generation it doesn't do much good. Our migration
system is somewhat automated and developers migrate from test to QA on
their own. I've tried to make them aware of this situtation and have
them regenerate the dialog on the source system, but they seldom do and
it can lead to time-date stamp problems.


#27 Make Global V AREA PURGE
Recent changes with the DCMT command causes SHARED cache to be flushed
when you vary an area from OFL to UPD. Following a problem we had, apar
QO46103 was created and shared cache is now flushed when you go from OFL
to RET. I thought the next extension would be to do the same for PURGE.
If you are in a data sharing environment you would want the buffers for
all the CVs to be flushed after a batch local job. We run batch local
with the database in retrieval mode in all CVs. We tolerate dirty reads
for some minor databases. We do a DCMT V AREA PURGE as the last step of
the batch job. With data sharing V AREA PURGE is as much a global
function as the vary area RET/UPD/OFL. We would like an enhancement to
the command to make it global or at the very least a parameter on the
command to do a global purge if needed without having to change the area
access mode


#28 ODBC Access Checked
ODBC-access to IDMS Database from a C/S-Application to be controlled by
an application specific code. To access the IDMS-Database by a front-end
C/S-application security today can be checked by User-ID and Password on
schema-level. Users who have been given access to a IDMS-record
therefore can access this record by any application including e.g.
MS/Access without the plausibility checks and navigation of the original
C/S application. We recommend a solution, where the C/S application is
sending an internal and encrypted access code to CA Server. This
Application Access Code should be checked against a table or module
which is maintained by a DBA. (Remark: For an interim solution outside
the IDMS-Server Standard today we use the Account Code as a part of the
ODBC-sign-on-procedure and an assembler module in User-Exit #28 in CA
IDMS Server)

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Third Party Vendors for TCP/IP IDMS Access
"Why not use the TCP/IP driver that is available with IDMS-DC as of Release
16.0? We're already using it with good results in Production - in one case
to access a Java application that returns data from an Oracle database to
our IDMS-DC ADS/O applications!

Cheers- Gary

Gary Cherlet
Justice Technology Services
Telephone +61 (0)8 8226 5199
Facsimile +61 (0)8 8226 5311
Mobile +61 (0)41 333 1613
MailTo:cherlet.gary@saugov.sa.gov.au

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original transmission
and its contents.
Confidentiality: This e-mail may contain confidential information which
also may be legally privileged. Only the intended recipient(s) may access,
use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are those
of the sender, not Justice Technology Services.
Computer Viruses: It is the recipient's responsibility to check the e-mail
and any attached files for viruses.

Outcomes