headers
John Jenkins | 1 Aug 2008 01:27

RE: [U2] UniData PROC tip: DB command

And a few more PROC commands for the die-hards:
(I love them ! (sorry Wally !!)
(from memory - I think I got it OK)
BTW: 
H = "Hollerith"
O=Output literal display text that follows
Sn -set input buffer position to n (no blanks allowed in most flavours - a
bit like var<-1>="xx")
IP: - Input (key data) at current input buffer position with a colon prompt
IP %1 input (key data) into input buffer position 1

%n - input buffer position n
#n - output buffer position n
&m.n - file buffer m, attribute n - attribute 0 is the ID
!n - Select buffer n
M - a "mark" cann be used to go FORWARD (G F) or BACKWARD (G B) to previous
or next mark (bad practice - but you can do it)
C - a comment
RI / RO - reset input or output buffer
F-CLEAR n - clear file buffer n
F-OPEN n - open file buffer n to the specified file - if the open fails the
next statement is executed otherwise it skips one statement
F-READ n - reads specified record into file buffer n - if the read fails the
next statement is executed otherwise it skips one statement
STON - stack on
X - exit with message
MV x y- move into buffer x as specified in y (buffer or literal)
F;%1;C1;+;?%1 - example of RPN math - adding one to input buffer 1 in this
example:
e.g. PUSH %1; PUSH character 1; ADD top two stack entries - POPPING them and
(Continue reading)

Permalink | Reply | 11 comments |
headers
Francis Bennett | 1 Aug 2008 04:56
Picon

Re: [U2] UniData PROC tip: DB command

I have an original R83 manual (dark grey and red with white stripes) - if
anyone has a major problem with PROC (or BASIC or anything else for that
matter) I could look it up.

Francis
  ----- Original Message -----
  From: John Jenkins
  To: u2-users <at> listserver.u2ug.org
  Sent: Friday, August 01, 2008 9:27 AM
  Subject: RE: [U2] UniData PROC tip: DB command

  And a few more PROC commands for the die-hards:
  (I love them ! (sorry Wally !!)
  (from memory - I think I got it OK)....
-------
u2-users mailing list
u2-users <at> listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Permalink | Reply | 1 comment |
headers
MAJ Programming | 1 Aug 2008 05:22
Picon

Re: [U2] UniData PROC tip: DB command

What is the point of this PROC dissertation. If it was for us die-hards,
then we already know this. If it's for the newbies, then it
would/should/could scare the hell out of them.

Since you brought it up, you forgot the ( command, the [ command, the GSUB
command, the RTN command, the '[] nnn' command, the concatenate with the MV
command, the multiple MV command, and the whole boatload of user-exits with
their cryptic syntax.

Also is pattern matching in IF commands, different IF commands, multiple
statement separators, multiple answer separators, ICONV and OCONV, IH, L and
the A"5 command.

I use PQN proc (nee Microdata) every week with a true Microdata client and
often with a UD client with some Microdata switch turned on.

Microdata advanced PQ proc to PQN while regular Pick was advancing with
EXECUTE. IMHO, EXECUTE won and Microdata faded into the sunset. (They had a
few other programming shortcomings that are clearly deficient by comparison
today).

My %2 cents
Mark Johnson
----- Original Message -----
From: "John Jenkins" <u2guru <at> btinternet.com>
To: <u2-users <at> listserver.u2ug.org>
Sent: Thursday, July 31, 2008 7:27 PM
Subject: RE: [U2] UniData PROC tip: DB command

> And a few more PROC commands for the die-hards:
(Continue reading)

Permalink | Reply | 6 comments |
headers
MAJ Programming | 1 Aug 2008 05:38
Picon

Re: [U2] UniData PROC tip: DB command

R83 ain't gonna help too much if the Proc ventured into the PQN (versus PQ)
category.

Microdata and regular Pick (R80, 83, 90, AP, D3) were in sync with their PQ
commands during the Jurrasic Pick era. In 1979 MCD introduced PQN with its
extended features as shown in the earlier email. I was there at that
roll-out.

In fact, Microdata PQN procs could not call PQ procs and vice-versa. They
were 2 separate interpreters. There were some tricks around this.

Over the years the non-Microdata flavours stepped up their PQ-level procs (T
command comes to mind instead of U01A6) but focused more on the EXECUTE
command. This opened the door to making the English Commands available to
regular Data/Basic instead of trying to bump up Proc to behave more like
Data/Basic. Since Proc was still interpreted, non-indentable and cryptic, it
was relegated to being a Menu handler or jobstream handler like Batch Files
(Not to be confused with Batch Updating). Some jobstreams were so obvious
that the paragraph interpreter was created to save all of the "H" and "P"
command usage.

(Sidebar. MCD also created the "A" correlative and had the edge for a few
years on the other earlier native systems. They caught up eventually).

But the damage was done as virtually every system that was written pre-1990
had procs scattered throughout. Every one of my clients still has procs.
Unless there was a complete re-write, it will still retain this legacy code
and language.

I don't know about UV but UD has a setting that allows true-PQN proc
(Continue reading)

Permalink | Reply | 0 comments |
headers
Clifton Oliver | 1 Aug 2008 06:05

Re: [U2] UniData PROC tip: DB command

Just as a point of history, EXECUTE was invented by the Devcom team  
who wrote what became Prime INFORMATION. Our in-house motto was  
"PROCs are Crocks."

Regards,

Clif

On Jul 31, 2008, at 8:22 PM, MAJ Programming wrote:

> Microdata advanced PQ proc to PQN while regular Pick was advancing  
> with
> EXECUTE. IMHO, EXECUTE won and Microdata faded into the sunset.  
> (They had a
> few other programming shortcomings that are clearly deficient by  
> comparison
> today).
-------
u2-users mailing list
u2-users <at> listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Permalink | Reply | 5 comments |
headers
Dennis Bartlett | 1 Aug 2008 13:35
Picon

RE: [U2] OPEN fname ... ELSE STOP 3000, fname

We did it on a library system for having multiple language support, that way
the user login loaded the ERRMSG file and all errors were in the local taal
(language)

Since the legacy app is used even today, on both D3 and UV, it still works
off an ERRMSG file, only the access method now is via a special subroutine
to log the error and abort gracefully..

Speaking of that, the original URICA library system, used extensively in the
UK and a couple in SA, was written in PROC... And used this ERRMSG idea in
it too

-----Original Message-----
On Jul 31, 2008, at 12:20 PM, Stevenson, Charles wrote:

> I've got old, old code riddled with "STOP 3000, filename".
> ERRMSG 3000 does not exist on UV 10.2.6.
> Did it ever exist on UV?
> What version of Pick did this come from.
-------
u2-users mailing list
u2-users <at> listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Permalink | Reply | 0 comments |
headers
MAJ Programming | 1 Aug 2008 15:19
Picon

Re: [U2] UniData PROC tip: DB command

I first ran into Execute on an Ultimate. If I recall correctly, it may have
been 1983?

I agree that Proc is dead and should be retired/replaced. But since it's
still there, it can't fully disappear.

I have been often labeled a PROCtologist by accidentally becoming very good
with Procs back in the day. Unfortunately there is no clear simple
replacement and/or 'replacement over time' that occurs when replacing F
corelatives with A's or retiring Batch processes.

Mark Johnson

----- Original Message -----
From: "Clifton Oliver" <lists <at> oliver.com>
To: <u2-users <at> listserver.u2ug.org>
Sent: Friday, August 01, 2008 12:05 AM
Subject: Re: [U2] UniData PROC tip: DB command

> Just as a point of history, EXECUTE was invented by the Devcom team
> who wrote what became Prime INFORMATION. Our in-house motto was
> "PROCs are Crocks."
>
>
> Regards,
>
> Clif
>
> On Jul 31, 2008, at 8:22 PM, MAJ Programming wrote:
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Baker Hughes | 1 Aug 2008 18:58
Favicon

RE: [U2] UniData PROC tip: DB command

The man (person) who writes a PROC interpreter/conversion utility that can take a PROC and turn it into
either Basic, or a PAragraph, will have a product to sell... esp. if it can decipher all the PROC nuances and
tricks that have been introduced over the years.  Same goes for a tool to convert A correlatives to
I-descriptors.  But pity the wretch that is assigned the task of writing the tool to convert F
correlatives.  We'll sooner inhabit Uranus.

-Baker

/snip

I have been often labeled a PROCtologist by accidentally becoming very good with Procs back in the day.
Unfortunately there is no clear simple replacement and/or 'replacement over time' that occurs when
replacing F corelatives with A's or retiring Batch processes.

Mark Johnson
-------
u2-users mailing list
u2-users <at> listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Permalink | Reply | 3 comments |
headers
jpb-u2ug | 1 Aug 2008 18:53
Picon
Favicon

[U2] Available printer memory exceeded

Last night during our month end batch process it aborted the proc when we
got "Available printer memory exceeded" during one of the programs. I ran
the program this morning and it ran without getting the error, same program,
same data files. Can anyone tell me where I could look to keep it from doing
this? It has always run without problems in the past, it only runs at month
end, but there were some minor changes made to the program that shouldn't
have caused any problems and don't when run by itself.

Jerry Banker

Senior Programmer Analyst

IBM Certified Solutions Expert

Affiliated Acceptance Corp
-------
u2-users mailing list
u2-users <at> listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Permalink | Reply | 0 comments |
headers
Brutzman, Bill | 1 Aug 2008 20:31

RE: [U2] Available printer memory exceeded

1. What kind of printer is it?
2. Is there a JetDirect or some other print server involved?
3. What OS is it running on?
4. Is it UniData or UniVerse?

--B

-----Original Message-----
From: owner-u2-users <at> listserver.u2ug.org
[mailto:owner-u2-users <at> listserver.u2ug.org]On Behalf Of jpb-u2ug
Sent: Friday, August 01, 2008 12:54 PM
To: u2-users <at> listserver.u2ug.org
Subject: [U2] Available printer memory exceeded

Last night during our month end batch process it aborted the proc when we
got "Available printer memory exceeded" during one of the programs. I ran
the program this morning and it ran without getting the error, same program,
same data files. Can anyone tell me where I could look to keep it from doing
this? It has always run without problems in the past, it only runs at month
end, but there were some minor changes made to the program that shouldn't
have caused any problems and don't when run by itself.

Jerry Banker

Senior Programmer Analyst

IBM Certified Solutions Expert

Affiliated Acceptance Corp
-------
(Continue reading)

Permalink | Reply | 503 comments |

Gmane