ca.portal.admin

Looking for SUBSCHEMA-RECNAMES

Discussion created by ca.portal.admin on Oct 3, 2009
Hi all,
=20
We have a number of DC-COBOL programs that include in their Working Storage=
section lines such as COPY IDMS SUBSCHEMA-RECNAMES or COPY IDMS SUBSCHEMA-=
SSNAME
=20
The DMLC pre-compiler expands these quite happily, so obviously they exist =
in some dictionary. However, I cannot find them using IDD or IDMSDDDL DIS =
REC SUBSCHEMA-RECNAMES V HIGH. I have searched all of the usual places: ou=
r default secondary dictionary, SYSDIRL, APPLDICT, SYSTEM.
=20
Does anybody have any idea where these puppies are hiding?
=20
Thanks,
=20
Jim Ritterbusch
Database Administrator
GE Capital
83 Wooster Heights Rd
5th Floor South
Danbury, CT 06810
T (203) 546 4370
=20
=20
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Looking for SUBSCHEMA-RECNAMES
"There are a variety of COPY IDMS ..... options, each of which will copy more or less of the communication areas required to access an IDMS database. The areas required are listed below:

SUBSCHEMA-CTRL: the primary communication control block with DBMS, contains run-time call parameters, current DBKEY, ERROR-STATUS and so forth. This actually exists as an IDMS record - there are different version depending on the PROTOCOL being used. The ERROR-STATUS field has a predefined set of 88 levels for convenient error condition checks (you don't need to remember the numeric codes). I have seen some shops modify this record to include new 88 levels for error conditions that are commonly tested for at those shops. COPY IDMS forms that include this data area:
SUBSCHEMA-DESCRIPTION, SUBSCHEMA-CONTROL, SUBSCHEMA-CTRL.

SUBSCHEMA-SSNAME: the 8 character literal containing the subschema name - used in the Run Unit BIND but that is the only CALL that it is required for. COPY IDMS forms that include this data area:
SUBSCHEMA-DESCRIPTION, SUBSCHEMA-CONTROL, SUBSCHEMA-SSNAME.

SUBSCHEMA-RECNAMES: copies the literal names of all database records included in the subschema. The actual data name (if you need to reference it) is SRnnnn, where the nnnn is the schema assigned Schema Record ID (SRID). The literal itself contains the record name associated with the given SRID. COPY IDMS forms that include this data area:
SUBSCHEMA-DESCRIPTION, SUBSCHEMA-CONTROL, SUBSCHEMA-NAMES, SUBSCEHMA-RECNAMES.

SUBSCHAMA-AREANAMES: copies the literal names of all database areas included in the subschema. The actual data name (if you need to reference it) is the same as the AREA Name. The literal itself contains the area name. COPY IDMS forms that include this data area:
SUBSCHEMA-DESCRIPTION, SUBSCHEMA-CONTROL, SUBSCHEMA-NAMES, SUBSCHEMA-AREANAMES.

SUBSCHAMA-SETNAMES: copies the literal names of all database sets included in the subschema. The actual data name (if you need to reference it) is the same as the SET Name. The literal itself contains the set name. COPY IDMS forms that include this data area:
SUBSCHEMA-DESCRIPTION, SUBSCHEMA-CONTROL, SUBSCHEMA-NAMES, SUBSCHEMA-SETNAMES.

SUBSCHEMA-RECORDS: copies the (IDD Record Synonym) descriptions of all records contained in the subschema

Too look at it another way - here is what is copied by various ""cumulative"" forms of the COPY command:

SUBSCHEMA-DESCRIPTION copies SUBSCHEMA-SSNAME, SUBSCHEMA-CTRL, SUBSCHEMA-RECNAMES, SUBSCHEMA-SETNAMES, SUBSCHEMA-AREANAMES, SUBSCHEMA-RECORDS.

SUBSCHEMA-CONTROL copies SUBSCHEMA-SSNAME, SUBSCHEMA-CTRL, SUBSCHEMA-RECNAMES, SUBSCHEMA-SETNAMES, SUBSCHEMA-AREANAMES.

SUBSCHEMA-NAMES copies SUBSCHEMA-SSNAME, SUBSCHEMA-RECNAMES, SUBSCHEMA-SETNAMES, SUBSCHEMA-AREANAMES.

Which form of the COPY statement you use depends on how much control of where you want the different areas copied into - some into Working Storage and some into Linkage Storage for example!

Do not forget the COPY IDMS SUBSCHEMA-BINDS - this will initialise PROGRAM-NAME in SUBSCHEMA-CTRL, create a BIND RUN UNIT statement and will create BIND RECORD statements either for all records in the subschema, or if PROTOCOL .... MANUAL ... has been specified will create Record BIND statements only for the explicitly copied IDMS Records (with the COPY IDMS SUBSCHEMA-RECORD statements).

Sections 4.4 and 4.5 of the CA-IDMS Reference - Cobol manual restates all of this, slightly differently, again.

HTH - cheers - Gary

Gary Cherlet
Justice Technology Services
Department of Justice, SA Government

"""""""" Telephone +61 (0)8 8226 5199
@@ Facsimile +61 (0)8 8226 5311
> Mobile +61 (0)41 333 1613
\/ MailTo:gary.cherlet@sa.gov.au

Murphy says:
1. ""Everything is a system.""
2. ""Everything is part of a larger system.""
3. ""The universe is infinitely systematized both upward (larger systems) and downward (smaller systems).""
4. ""All systems are infinitely complex (the illusion of simplicity comes from focusing attention on one or a few variables).""

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