This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C16793.76E1FDA0 Content-Type: text/plain; charset="iso-8859-1" Environment: PowerHouse 8.39C running under MPE/iX 6.5pp2+ Good Afternoon (if your on the western side of the pond then Good Morning), I don't know about anybody else but I tend to put as much information into our dictionary as possible. It helps when the two main systems you interface with are written by a third party. Every time we find out anything new about how a field or record is used then we update the dictionary. I would estimate that about 60% of our production dictionaries consists of DESCRIPTION, BEGIN...END STRUCTURE and ITEM ... REDEFINES statements. For example: We recently found out that there is an 'obsoleted date' field on our product master file. It occupies the location that used to hold a 'bulk location' address. The supplier didn't bother to change the database so it is still called BULK-LOCATION instead of OBSOLETED-FLAG. This is one of many features on our databases that PowerHouses dictionary has helped us with. One of our software suppliers needed structural information about one of the databases that did not belong to them. I printed of a copy of the database schema to send to them and then realised that it only showed the physical structure not the logical structure. That info was held in one of our dictionaries. I then spent over two hours extracting the FILE, RECORD and ELEMENT entries from a QSHOW listing that I had sent to a disc file. Now a request for help HELP!!!!!! Anybody have a script/program/anything, that they are willing to pass on, that will make this easier for me in the future? regards, ***************************** Robert W.Mills, Systems Development Manager, Windsong Services Electron House, Cray Avenue, St. Mary Cray, Kent BR5 3PN, ENGLAND Tel: +44 (0)1689.870622 x 3005 Fax: +44 (0)1689 899026 robert.mills@windsong-services.co.uk ******************************** The thoughts, comments, and opinions expressed herein are mine. They do not reflect those of my employer, nor anyone else. ******************************** ***Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ------_=_NextPart_001_01C16793.76E1FDA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">Extracting data from a PHD Environment: PowerHouse 8.39C = running under MPE/iX 6.5pp2+
Good Afternoon (if your on the = western side of the pond then Good Morning),
I don't know about anybody = else but I tend to put as much information into our dictionary as = possible. It helps when the two main systems you interface with are = written by a third party. Every time we find out anything new about how = a field or record is used then we update the dictionary. I would = estimate that about 60% of our production dictionaries consists of = DESCRIPTION, BEGIN...END STRUCTURE and ITEM ... REDEFINES = statements.
For example: We recently found = out that there is an 'obsoleted date' field on our product master file. = It occupies the location that used to hold a 'bulk location' address. = The supplier didn't bother to change the database so it is still called = BULK-LOCATION instead of OBSOLETED-FLAG. This is one of many features = on our databases that PowerHouses dictionary has helped us = with.
One of our software suppliers = needed structural information about one of the databases that did not = belong to them. I printed of a copy of the database schema to send to = them and then realised that it only showed the physical structure not = the logical structure. That info was held in one of our dictionaries. I = then spent over two hours extracting the FILE, RECORD and ELEMENT = entries from a QSHOW listing that I had sent to a disc file. =
Now a request for = help HELP!!!!!!
Anybody have a = script/program/anything, that they are willing to pass on, that will = make this easier for me in the future?
regards,
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Robert W.Mills, Systems Development Manager, Windsong = Services
Electron House, Cray Avenue, St. Mary Cray, Kent BR5 3PN, = ENGLAND
Tel: +44 (0)1689.870622 x 3005 Fax: +44 (0)1689 = 899026
robert.mills@windsong-services.co.uk
ssssssssssssssssssssssssssssssss
The thoughts, comments, and opinions expressed herein are = mine.
They do not reflect those of my employer, nor anyone = else.
ssssssssssssssssssssssssssssssss
***Confidentiality Notice: This e-mail message, including any = attachments, is for the sole use of the intended recipients and may = contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. If you are not = the intended recipient, please contact the sender by reply e-mail and = destroy all copies of the original message.
------_=_NextPart_001_01C16793.76E1FDA0--