In addition to product development and trips out of town I've had two
primary systems die in the last two weeks and require complete
re-installation - no time for lists, thank the Lords of Kobol for backups.
But I'm back now and what do I see in the U2 list? Questions about D3... My
My, gone a little while and the world turns upside down.
Anyway:
1) PQN was never ported to D3 as it was never a product of Pick Systems.
Big HOWEVER: RPL is still found on many D3/*nix systems and is fully
supported by the Realtime Software Corporation with new sites being
installed all the time. (Not truly a lost art.) For the uninitiated, RPL
is essentially compiled PQN's but only at the file level, not the MD/VOC
level. So rather than your code being written and compiled in BASIC it's in
RPL. If you have PQN code like Mark posted below, then RPL is the only way
to go these days, and it's only available for D3. It's actually very fast
code, though not pretty. Those familiar with older RPL should note that
there are now 256 file buffers and assorted other enhancements -
applications are no less complex than those in BASIC and I've interfaced RPL
apps with Web Services and other high-end communications interfaces. So no,
PQN isn't available in the MD in D3 in standard platforms.
001=PQ, 002=HTIME, 003=P ... that should work.
2) Mark's problem seems to be that he was modifying the MD and M/DICT items.
These items are both Q-pointers that point back recursively to the MD/VOC.
Do NOT change where these items point! The MDS points to all MD's in the
system, like a root directory points to all directories under it. Do NOT
manually change where MDS items point!
HTH,
Tony
(Former DBMS Product Manager for Raining Data, including D3)
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of Mark Johnson
> Sent: Friday, May 07, 2004 9:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [U2] D3 Master Dictionary
>
> Technically, no. D3 does not support PQN in the truest sense of the "N".
>
> PQN came out in 1979 as an enhanced version of Proc from Microdata, hence
> the N as New. PQ and PQN procs could not participate in the () program
> transfer. You had to get tricky instantiating a contrary proc from the
> source proc's style by treating it as a verb instead of a proc transfer.
>
> There are real specific differences between PQN and PQ proc the likes that
> most MV people have not been exposed to. I've only seen Microdata-level
> proc
> on UD or UV as microdata flavor. Perhaps there's more, but not likely.
>
> The 'features' in PQN proc that make it different than PQ are in a few
> categories. The most obvious is the MV (move) command, the readnext
> concept
> and the file handling commands.
> MV %1 "MARK"
> MV #5 "MARK"
> MV &1.5 "MARK","RANDY","BOB"
> MV %1 !1
> PQ-SELECT 1
> F-OPEN, F-READ, F-CLOSE
> Plus there was GO F and GO B for localized unlabeled labels.
>
> Everyone else focused on EXECUTE/PERFORM while MCD developed the PQN to
> handle some of these advanced features. Now, writing procs is a lost art.
>
> my 1 cent.
-------
u2-users mailing list
[EMAIL PROTECTED]
http://www.u2ug.org/listinfo/u2-users
