× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I sent you them off-list.

99% of my SQL/400 programming is via embedded inside RPG.

Occasionally I use STRSQL with SELECT to obtain some data, then SAVE
the successful session to get the successful code to embed in some
program.

My main current focus struggle is review of EOY needs, make sure software
ready, then as I test stuff, this leads people ideas for further
improvements. Inventory unused in some time frame, slow moving inventory.
Much of this data derived via SQL embedded in RPG.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of
Margareth Sere
Sent: Sunday, November 07, 2010 9:38 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] SQL Cheat Sheets RE: Item with last transaction date

Hi Al,
I think these stuff is good and I think I can use it as query/400
alternative as I am struggling on SQL/400
Can I also request for a copy of all these docs.

TIA!

Regards,
Margie

On Fri, Oct 22, 2010 at 2:05 AM, Al <macwheel99@xxxxxxxxxx> wrote:

Another alternative to query/400 or RPG is SQL/400.

I have been to a couple classes in SQL and still have some class hand-outs
from it as Word documents. I could send you off-line if you interested.
They are:

171 k SQL Codes
85k SQL Data Types
53k SQL Examples
220k SQL Roadmap
496k SQL Tech Ref
65k SQL RPGLE Examples

Also see below
61 k Math 400

This is SQL/400 programming in general. It is not BPCS specific.

The third one has examples which can also be used in Query/400, such as
sub-stringing a date.

Plus it reminds me of another Query Tip I neglected to mention earlier.
When you grab files in Query, they get labeled T01 T02 T03 etc. I like to
relabel them as I (for Item Master) I1 (for IIML01) C (for cost or
customer
file) T (for ITH transactions) etc. This makes it easier later seeing
which
file is which on the other Query screens.

If you are not an RPG programmer, the first one (SQL Codes) will be
totally
Greek to you, because it is a list of the various "error" condition codes
that are fed back to an RPG program when you use embedded SQL, that your
program might want to test for.

The Technical Reference explains what you have to have from IBM for this
stuff to work, compares SQL to DDS, has an inventory of functions
available,
the various things you can do, and their rules.

The Roadmap is an essay or introduction for understanding SQL/400 on IBM
platform. It provides suggestions for additional reading up on the
subject.

If you ask for them, I will not send using the same e-mail address I use
for
BPCS-L because my ISP has been flickering out on me, which is a royal pain
when there's dozens of e-mails in the queue, or VPN to 400.

I also offer a seventh document.

61 k Math 400

This is a write-up by me, a few years ago, addressing the question of
which
functions I am able to get out of which programming languages I was
familiar
with on the 400 a few years ago. It compares: OPNQRYF in CL, query/400;
SQL/400; RPG; - their relative pros & cons from my perspective, since each
one offers stuff I not know how to do in the others. It also mentions a
few
other alternatives that me not proficient in. I wrote this so long ago
that
there are references in there I forget the details of.

Maybe one person here who asks for this stuff, can then inform the group
whether Al's offer is any damn good, considering it is not current stuff.

-
Al Mac



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.