The LF must be over one PF only. When we filled our data dictionary PF, we renamed it volume 1 and created PF volume 2. Then we created an LF with the old name over these two volumes so that the RPG that copybook the dictionary didn't need changing.
No one using a dictionary for their CLP out there?
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : vendredi 6 février 2009 14:33
À : Midrange Systems Technical Discussion
Objet : Re: Declaring a data dictionary in a CLP
Well, with WDSC I can either not display the option 10 messages, but then again, it sorts by severity level, descending.
What do you mean, "doesn't seem to be possible with DCLF"? Are you having an error, like too many fields or are you under the impression that DCLF doesn't support LF's?
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
David FOXWELL <David.FOXWELL@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/06/2009 07:00 AM
Subject:
Declaring a data dictionary in a CLP
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
I just discovered the parameter STG(*DEFINED) in the DCL statement.
I added our database dictionary PF in a DCLF and declared a variable based on on from the dictionary. As we have 2 PF that make up our dictionary ( the first one is full) I needed two DCLF to declare the whole dictionary.
Our RPG programs use a single LF that points to both the PF of the dictionary which doesn't seem to be possible with DCLF.
The down sides I've found are : I need to declare 2 OPNID, so I have to know which PF or volume of the dictionary I'm using. Also, when searching a compiled source in SEU split screen with *ERR, there are an awful lot of messages with gravity 10 that get in the way. The names of the zones referenced in my case would be limited to 8 as a minimum of 2 characters are used for the prefix of the program variable.
Any thoughts?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.