RE: [U2] SAP Migration

2008-07-31 Thread Allen E. Elwood
Hey Kebbon,

I've done this before and basically what the diff is between sql and mv is
the mv's.

So let's say you have an order, and on that order are order lines.  sql will
only be able to handle the single value data from the order and that would
go into one ascii file.

The order lines would need to be broken down into their own records in a
separate file.  The first field of each line would be order*line.nbr, and
then the rest of the single value info for that line would be the rest of
the record - tab delimited.  If there was multiple delivery data for each
line in a sub-valued-group, that too would then need to be broken down into
it's own file with the first field being order*line*delivery.

When this gets sucked up into SQL the first field becomes the index that
points to a record number in a file where the rest of the data is.

Good old ISAM(stinky old ISAM actually)

What I did was to write a program that would analyze the dicts for each file
and pull them into groups of groups using the associated field (this was on
a database where the dicts where actually maintained specifically so it
would be SQL compliant).

Then after manually reviewing this document with the conversion team, we'd
decide which fields were needed and I would then tweak the output from the
groups of groups file setting flag to note it needed to be included and what
order it was to be in - like if it was to be the third field then I'd put in
a 3, even though it might have been the attr in the original file.

Then run another program that would build the INCLUDES for the fields that
were needed and then stick that into a skeleton program, and run another
program to tweak the file names in the skeleton program so it would be
specific to the file being downloaded and in the order desired.

This allowed me to only write a few programs, so that once the decision was
made as to what fields to include and their order, I just had to do a little
data entry, run a few routines and bingo, download completed.  Even so it
took months to go through the motions to create all the programs.  Since
they were in their own library, I then wrote a program that would read that
library and execute all the programs in sequence so that on the cutoff date
the operator wouldn't be able to forget anything.

It was a lot more work for the guys on the SQL side.  Three guys had to be
hired to put all the stuff into the SQL files that I was creating from the
MV side.  So much for *upgrading* their database.  You'd think they would
have gotten a clue that they were spending three times as much to convert TO
the new database as it took to convert FROM the old database, but no.

hth,

Allen E. Elwood
www.tortillafc.com
Quality Code Since 1978


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kebbon Irwin
Sent: Wednesday, July 30, 2008 10:44
To: u2-users@listserver.u2ug.org
Subject: [U2] SAP Migration


We have a client that has been purchased by another company and they run
SAP.  We have been asked to assist in the migration process and to provide
specific data in both Excel and SQL format.  I must confess, I am not sure
what they mean by SQL format.  Is there a standard layout I should be
aware of?
TIA
Kebbon
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] [UniData/Windows] Proc wait not working.

2008-07-31 Thread George Smith
Try PP.



On Wed, Jul 30, 2008 at 3:12 PM, Kathleene M Hunter 
[EMAIL PROTECTED] wrote:

 Have a proc that I want to have it wait before executing the select but the
 PW is not working. Are there UDT.OPTIONS that cause this not to work.  This
 running on  Windows NT with UniData.  Below is the proc and the what
 happens
 when it runs.

 *
 Here is the PROC
 001: PQN
 002: O HERE
 003: HSELECT FIEL WITH ACCT
 004: PW
 005: 0 DONE
 *
 Here is the output
 HERE

 17 records select to list 0.

 DONE
 ***

 Why did  it not show what is going to execute  and wait until I pressed
 enter to execute.
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/




-- 
George Smith, Phoenix, AZ
Member of the Independent Computer Consultants Association since 1983
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UniData PROC tip: DB command

2008-07-31 Thread Dennis Bartlett
Kathleen

The way PROC works is that it stores data and commands in buffers, one of
which is also known as the stack. 
Execution is the process of moving these between input and output buffers.
If you've ever worked with assembler this will make perfect sense to you.

The D command displays data in a buffer.

Quoted from below:
* Proc is to move data between input and output buffers, 
using arguments passed from the command line, 
user-prompted input, and 
stored data and commands to build a TCL statement.

To run things you would push commands onto the stack (using H) and then
process them (using P). To store further things on the stack before running
a command, like answers to questions the command might ask, you would put in
a STON command (Stack On) and preload it in the next lines, until it hits a
P(rocess command).

This stack concept is the same used in BASIC when we want to run a command
and feed it pre-arranged answers (using DATA) to questions it might ask. 

Every data storage and excution place in a PROC is a buffer.

Quoted from below:
* H command places the literal string in the output buffer
* A command copies user input to the output buffer.
* P command sends the contents of the output buffer to the TCL
processor.


http://jdjua.com/sqlpickjbaseuniverse.htm
 Proc: Consist of TCL Commands : JCL and Shell Programming

* PROC processor:
* PROCLIB is a file that contains Procs supplied with the system.
* LISTPROCS is a system Proc that lists all the Procs in file PROCLIB in
dictionary format.
* SYSPROG account has additional Procs and programs stored in the
SYSPROG-PL (SPL is a synonym for it)  file.
* Proc (initial capitalization) refers to a procedure
* Proc is to move data between input and output buffers, using arguments
passed from the command line, user-prompted input, and stored data and
commands to build a TCL statement.
* TCL or INFO/ACCESS statements called Procs.
* Primary input buffer
* Secondary input buffer
* Primary output buffer
  o At any given time, one input buffer and one output buffer are
active
  o PROC Buffer. A buffer contains parameters which are delimited by
spaces. A buffer pointer points to the current parameter.
* Secondary output buffer (also known as the STACK)
* TCL Processor
* PQ to identify it to the system as a Proc
* H command places the literal string in the output buffer
* A command copies user input to the output buffer.
* P command sends the contents of the output buffer to the TCL
processor.
* O command displays a string of text on the user's terminal screen.
* IP command reads the information entered by the user into the input
buffer. It prompts for the input with a colon (:).
* GO 10 transfers control to the command line that is labelled 10
* X command terminates the Proc and returns control to the TCL processor
* IF command provides for conditional branching.
* C must be the first character on a comment line
* ()([DICT] filename proc-name): create Proc
* IT Command: Tape Input
* IH Command: replaces the current parameter in the input buffer with
text
* +/- Commands: + (add) command adds an integer to the current parameter
in the input buffer and the - (subtract) command subtracts an integer from
this parameter.
* RI Command: Reset Input
* F Command Moves the active input buffer pointer forward to the next
parameter.
* B Command Moves the active input buffer pointer backward one
parameter.
* S Command The S (set) command moves the active input buffer pointer to
a specific parameter.
* LIST CUSTOMERS WITH LAST-NAME = JOHNSON LAST-NAME FIRST-NAME STREET
CITY STATE : Access Statement: List Customers with Last name as JOHNSON with
other fields.
* SORT-ITEM MD WITH D/CODE = PQ: INFO/ACCESS command: sorts and
displays all items in the Master Dictionary whose first line is PQ.

A nice reference manual is
ftp://ftp.rainingdata.com/pub/mvBase/2.1/Documentation/ReferenceManual/procp
qx.pdf

Another place to look is
http://www.sierra-bravo.com/multivalue/d3reference/command/proc


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kathleene M Hunter
Sent: 31 July 2008 03:40 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UniData PROC tip: DB command

It not a buffer

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Ballinger
Sent: Wednesday, July 30, 2008 5:29 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] UniData PROC tip: DB command

R83 style for this is:

D0 - display all
D1 - display buffer 1
D2 - display buffer 2
etc

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

On Wed, Jul 30, 2008 at 4:46 PM, Wally Terhune [EMAIL PROTECTED] wrote:

 Kathleene's posting jogged my memory on this...

 DB (Display Buffers) command works in UniData PROCs. 

[U2] gfe check from unix?

2008-07-31 Thread doug chanco
in universe 10.1/10.2 (on aix) is it possible to check for GFE's or 
BLINK errros without going into universe?


any ideas/thoughts/suggestions welcomed!

thanks

dougc
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Green Software - Green Business

2008-07-31 Thread Susan Joslyn
Ross,
That's funny - and sad.  My sister lives in Norway - and maybe that explains
why I haven't heard of any other companies doing it. Maybe US companies are
concerned with just such a lawsuit!

Now who can I sue because the US has developed such a litigious reputation?

S


Date: Wed, 30 Jul 2008 19:00:48 +1000
From: Ross Ferris [EMAIL PROTECTED]
Subject:

As an observer from across the water, and given the litigious nature I
perceive pervading the US, I just wonder what will happen to this
initiative the first time an employee is hit  injured whilst travelling
to work? If the community had bike lanes and/or trails that were JUST
for bikes, it would be safer -- unless of course one of the bike riders
runs over an innocent pedestrian  I'm probably just FAR too cynical
:-(

Ross Ferris
Stamina Software
Visage  Better by Design!
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] gfe check from unix?

2008-07-31 Thread Scott Ballinger
I think both uvfixfile and fixtool can be run from unix (you may need to run
as root).

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

On Thu, Jul 31, 2008 at 3:25 AM, doug chanco [EMAIL PROTECTED] wrote:

 in universe 10.1/10.2 (on aix) is it possible to check for GFE's or BLINK
 errros without going into universe?

 any ideas/thoughts/suggestions welcomed!

 thanks

 dougc
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] gfe check from unix?

2008-07-31 Thread Dan Goble
Run the fixtool command from the $uvhome/bin without the fix option and
it will do diagnostics

fixtool -filepath Path_to_file -file name_of_file

Dan Goble
Systems Administrator
RATEX Business Solutions, Inc.
(800) 417-2839 ext. 4116
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UniData PROC tip: DB command

2008-07-31 Thread Susan Lynch

Wally,

Thank you for that - as far as I recall, this is unique to UniData, and 
something I have not seen documented anywhere!


Always nice to learn something new!

Susan Lynch
F W Davison  Company, Inc.
- Original Message - 
From: Wally Terhune [EMAIL PROTECTED]

To: u2-users@listserver.u2ug.org
Sent: 07/30/2008 7:46 PM
Subject: [U2] UniData PROC tip: DB command



Kathleene's posting jogged my memory on this...

DB (Display Buffers) command works in UniData PROCs. Very helpful for
debugging PROC.
I think this is unique to UniData? (MV seasoned vetrans care to comment?)

DB on a line all by itself will display all buffers (varies for PQN vs PQ
proc).
Once you see all of the buffer names, you can just display one.
For instance, to display the primary input buffer:

DB PIB

Haven't fielded a support case with PROC questions in years, though. 
(IIRC)

regards,

Wally Terhune   Mark your
U2 Support Architectcalendar!
IBM Information Management Software
Tel: (303) 773-7969 T/L
656-7969
Mobile: (303) 807-6222
Email: [EMAIL PROTECTED]
http://www.ibm.com/software/data/u2/support

[demime 1.01d removed an attachment of type image/jpeg which had a name of 
22457278.jpg]

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] SAP Migration

2008-07-31 Thread Brutzman, Bill
One trick is to use ^ delimeted mv-data within a SQL field.  I believe that
Microsoft 
has some functionality for something like this technique in newer versions
of their SQL product.

--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Green Software - Green Business

2008-07-31 Thread George Land
Here in the UK there is a Government scheme under which you can buy a
bicycle tax free so long as your employer has signed up.  I don't know the
details or anyone who has done it though.

George


On 31/07/2008 11:27, Susan Joslyn [EMAIL PROTECTED] wrote:

 Ross,
 That's funny - and sad.  My sister lives in Norway - and maybe that explains
 why I haven't heard of any other companies doing it. Maybe US companies are
 concerned with just such a lawsuit!
 
 Now who can I sue because the US has developed such a litigious reputation?
 
 S
 
 
 Date: Wed, 30 Jul 2008 19:00:48 +1000
 From: Ross Ferris [EMAIL PROTECTED]
 Subject:  
 
 As an observer from across the water, and given the litigious nature I
 perceive pervading the US, I just wonder what will happen to this
 initiative the first time an employee is hit  injured whilst travelling
 to work? If the community had bike lanes and/or trails that were JUST
 for bikes, it would be safer -- unless of course one of the bike riders
 runs over an innocent pedestrian  I'm probably just FAR too cynical
 :-(
 
 Ross Ferris
 Stamina Software
 Visage  Better by Design!
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/


**
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify us immediately on +44 
(01952) 214000 or at [EMAIL PROTECTED] . Please delete and destroy any copies 
in any format of this email you may have received in error. The recipient 
should note that the views contained or expressed within this correspondence do 
not necessarily reflect those of APT Solutions Limited , it subsidiaries, 
affiliates or associates. This email and any attachments are not guaranteed to 
be free from so-called computer viruses and it is recommended that you check 
for such viruses before down-loading it to your computer equipment. It is the 
responsibility of the recipient to ensure that the onward transmission, opening 
or use of this message or any attachments will not adversely affect their 
systems or data.

Registered Office:- Stratum House, Stafford Park 10, Telford, Shropshire, TF3 
3AB

Registration Number:- 2228445

Place of Registration: England  Wales
**
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Green Software - Green Business

2008-07-31 Thread Brenda Price
Drive 55?  Ha!  More like 60-70 or 25-40!  I don't know what is worse
getting tailgated by the high speeders, or by the line of traffic behind
you.  Driving in the middle of the road, passing on curves regardless of
whether they are going uphill or downhill. Then you have the people that
ignore the fact someone else is already in their lane and pull out and
go no where.  I just love meeting dump trucks flying around a curve
where by the time they complete the curve they are halfway on my side of
the road.  No shoulders, narrow roads.  If you get car sick easily don't
come here! 

If I lived just a little closer and didn't have to cross a bridge over
the lake, I'd seriously consider riding my horse to work.

Brenda Price

-Original Message-
From: jpb-u2ug [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 31, 2008 10:20 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Green Software - Green Business

In our area of the Ozarks none of this would work because most of our
roads
are two lane and, except for the main roads, they are unpaved. We have
several people that have changed to driving motor cycles and higher
powered
motor scooters. Most of the people in this area have to drive 4 wheel
drives
because of the dirt roads and they know how to drive 55 mph on the
winding
roads so anything that is underpowered, like a bicycle, would be risking
their lives. 

Jerry

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
Sent: Thursday, July 31, 2008 5:28 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Green Software - Green Business

Ross,
That's funny - and sad.  My sister lives in Norway - and maybe that
explains
why I haven't heard of any other companies doing it. Maybe US companies
are
concerned with just such a lawsuit!

Now who can I sue because the US has developed such a litigious
reputation?

S


Date: Wed, 30 Jul 2008 19:00:48 +1000
From: Ross Ferris [EMAIL PROTECTED]
Subject:

As an observer from across the water, and given the litigious nature I
perceive pervading the US, I just wonder what will happen to this
initiative the first time an employee is hit  injured whilst travelling
to work? If the community had bike lanes and/or trails that were JUST
for bikes, it would be safer -- unless of course one of the bike riders
runs over an innocent pedestrian  I'm probably just FAR too cynical
:-(

Ross Ferris
Stamina Software
Visage  Better by Design!
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Green Software - Green Business

2008-07-31 Thread jpb-u2ug
In our area of the Ozarks none of this would work because most of our roads
are two lane and, except for the main roads, they are unpaved. We have
several people that have changed to driving motor cycles and higher powered
motor scooters. Most of the people in this area have to drive 4 wheel drives
because of the dirt roads and they know how to drive 55 mph on the winding
roads so anything that is underpowered, like a bicycle, would be risking
their lives. 

Jerry

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
Sent: Thursday, July 31, 2008 5:28 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Green Software - Green Business

Ross,
That's funny - and sad.  My sister lives in Norway - and maybe that explains
why I haven't heard of any other companies doing it. Maybe US companies are
concerned with just such a lawsuit!

Now who can I sue because the US has developed such a litigious reputation?

S


Date: Wed, 30 Jul 2008 19:00:48 +1000
From: Ross Ferris [EMAIL PROTECTED]
Subject:

As an observer from across the water, and given the litigious nature I
perceive pervading the US, I just wonder what will happen to this
initiative the first time an employee is hit  injured whilst travelling
to work? If the community had bike lanes and/or trails that were JUST
for bikes, it would be safer -- unless of course one of the bike riders
runs over an innocent pedestrian  I'm probably just FAR too cynical
:-(

Ross Ferris
Stamina Software
Visage  Better by Design!
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Green Software - Green Business

2008-07-31 Thread Kevin King
On Thu, Jul 31, 2008 at 7:50 AM, George Land [EMAIL PROTECTED]
 wrote:

 Here in the UK there is a Government scheme under which you can buy a
 bicycle tax free so long as your employer has signed up.  I don't know the
 details or anyone who has done it though.


But why would I buy a bicycle tax?  And even if it's free it's not much of a
bargain. ;-)

Yes, I'm joking. But it just goes to show how the American Congress looks at
things; exactly opposite of how it was intended, and as nonsensical as
possible.

I wonder how solid the internet connections are in Ireland?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Data Displayer

2008-07-31 Thread Kevin King
Hey, nice enhancement!

On Wed, Jul 30, 2008 at 8:55 AM, Brutzman, Bill [EMAIL PROTECTED]wrote:

 Kevin:

 Thanks for writing.  I was unClear on the syntax for the mask and I was
 hoping that someone would look at the code and flag the fluff.

 --B

 begin case
   case Width  20  ;  Width = 6
   case Width  1   ;  Width = 1
 case not(num(Width)) ;  Width = 6
 end   case
   Mask = 'L#' : Width
 print R.FileThis.Field, This.Count Mask : Red  : '_' : Grn :

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Kevin King
 Sent: Tuesday, July 29, 2008 8:41 PM
 To: u2-users@listserver.u2ug.org
 Subject: Re: [U2] Data Displayer


 No offense, but do you realize that big CASE statement could be reduced to
 three lines?

 If (Width LT 1 or Width GT 20) Then Width = 6
 Mask = L# : Width
 print R.FileThis.Field, This.Count Mask : Red : '_' : Grn :
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/




-- 
-Kevin
http://www.PrecisOnline.com
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


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

2008-07-31 Thread Clifton Oliver
Could it be a user (site) created ERRMSG file item? I knew one VAR  
that did that kind of thing for most of their packages error messages.



Regards,

Clif



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.

Just curious, more than anything else.
cds
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UniData PROC tip: DB command

2008-07-31 Thread John Jenkins
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
PUSHING the result on the stack; Store the top stack entry in %1

IF-  (test) - accepts one imperative and no ELSE. Multivalued lists of
conditions and simple actions allowed
T - (type a literal or buffer)  - he optional Sn displays n spaces, a B
displays a BELL, a + inhibits CRLF at the end of a display, a comma is
concatenate.

PQN
C Proc to test file pointers to see if they work and do count F and DIR
pointers.
C
C %1 holds count of files selected, %2 holds count of good file pointers
C %3 holds count of bad file pointers, %4 folds count of F pointers
C %5 holds count of DIR pointers, %6 is a work variable for the current file
name being processed
C
C Not run to check - so please be gentle on typos etc - just an example of
power
C if you want you can count multi-level files as well and say how many
sub-files in each one as an exercise (if you want to !)
C
T Starting file pointer verify at ,+
HDATE
P
RI
RO
F-CLEAR 1
F-OPEN 1 VOC
XBad Account - can't open VOC file
MV %1 0
MV %2 0
MV %3 0
MV %4 0
MV %5 0
HSSELECT VOC WITH F1 = F f DIR dir
STON
HPQ-SELECT 1
PH
10 MV %6 !1
IF # %6 G 30
F-READ 1 %6
G 20
IF 2.1 = F^253f^253DIR^253dir  G 15^25315^25317^25317
G F
15 F;%4;C1;+;?%4
G F
17 F;%5;C1;+;?%5
M
F;%1;C1;+;?%1
F-CLEAR 2
F-OPEN 2 %6
G 20
F;%2;C1;+,?%2
G 10
20 F;%3,C1,+,?%3 
T File ,%6, failed to open !,B
G 10
30 T S1
T Run complete at ,+
HDATE
P
T Checked ,%1, files: ,%2, good pointers and , %3, bad pointers
T %4, hashed files, ,%5, Directory files.

Regards

JayJay
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UniData PROC tip: DB command

2008-07-31 Thread Francis Bennett
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@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@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UniData PROC tip: DB command

2008-07-31 Thread MAJ Programming
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 A5 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 [EMAIL PROTECTED]
To: u2-users@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:
 (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
 PUSHING the result on the stack; Store the top stack entry in %1

 IF-  (test) - accepts one imperative and no ELSE. Multivalued lists of
 conditions and simple actions allowed
 T - (type a literal or buffer)  - he optional Sn displays n spaces, a B
 displays a BELL, a + inhibits CRLF at the end of a display, a comma is
 concatenate.

 PQN
 C Proc to test file pointers to see if they work and do count F and DIR
 pointers.
 C
 C %1 holds count of files selected, %2 holds count of good file pointers
 C %3 holds count of bad file pointers, %4 folds count of F pointers
 C %5 holds count of DIR pointers, %6 is a work variable for the current
file
 name being processed
 C
 C Not run to check - so please be gentle on typos etc - just an example of
 power
 C if you want you can count multi-level files as well and say how many
 sub-files in each one as an exercise (if you want to !)
 C
 T Starting file pointer verify at ,+
 HDATE
 P
 RI
 RO
 F-CLEAR 1
 F-OPEN 1 VOC
 XBad Account - can't open VOC file
 MV %1 0
 MV %2 0
 MV %3 0
 MV %4 0
 MV %5 0
 HSSELECT VOC WITH F1 = F f DIR dir
 STON
 HPQ-SELECT 1
 PH
 10 MV %6 !1
 IF # %6 G 30
 F-READ 1 %6
 G 20
 IF 2.1 = F^253f^253DIR^253dir  G 15^25315^25317^25317
 G F
 15 F;%4;C1;+;?%4
 G F
 17 F;%5;C1;+;?%5
 M
 F;%1;C1;+;?%1
 F-CLEAR 2
 F-OPEN 2 %6
 G 20
 F;%2;C1;+,?%2
 G 10
 20 F;%3,C1,+,?%3
 T File ,%6, failed to open !,B
 G 10
 30 T S1
 T Run complete at ,+
 HDATE
 P
 T Checked ,%1, files: ,%2, good pointers and , %3, bad pointers
 T %4, hashed files, ,%5, Directory files.

 Regards

 JayJay
 ---
 u2-users mailing list
 u2-users@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UniData PROC tip: DB command

2008-07-31 Thread MAJ Programming
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
commands to exist.

There was an earlier Microdata language called RPL that I've not heard of in
almost 30 years. Then there was those programmers who could create assembler
programs and MLOAD them. These are probably long gone as well. All of that
PIB and control block stuff was fascinating but unless you came from a
useful BAL background, you didn't have a chance. Am I showing my age?

My 2 cents.
Mark Johnson
- Original Message -
From: Francis Bennett [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, July 31, 2008 10:56 PM
Subject: 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@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@listserver.u2ug.org
 To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UniData PROC tip: DB command

2008-07-31 Thread Clifton Oliver
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@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/