RE: IBM on Monday introduced a free version of its DB2 database

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

Ummm, they do have DB2 Express-C for Linux POWER 64-bit.  That should
run in a Linux partition, no hardware required. 

http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=dm-db2e
xpress

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Tue, 31 Jan 2006 15:26:38 +1100
from: Kevin Wright <Kevin.Wright@xxxxxxxxxxxx>
subject: RE: IBM on Monday introduced a free version of its DB2
        database

>From what I have seen, which is admittedly very little, possibly on an 
>IXS,
FSIOP or whatever the PC under the hood is called - not on the iSeries
itself unless it suddenly runs on AMD or Intel based chips. Last time I
heard it was Power architecture :)

Regards,

Kevin Wright 

> -----Original Message-----
> From: Steve Richter [mailto:stephenrichter@xxxxxxxxx]
> Sent: Tuesday, 31 January 2006 3:13 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: IBM on Monday introduced a free version of its
> DB2 database
> 
> 
> On 1/30/06, Booth Martin <booth@xxxxxxxxxxxx> wrote:
> > "IBM on Monday introduced a free version of its DB2 database, a move

> > designed to win software developers over to its products.
> >
> > DB Express-C is the same database as IBM's commercial
> offerings but the
> > company places limits on what kind of hardware it can run on.
> >
> > It can be deployed on systems with two processor cores or up to two 
> > dual-core chips on Advanced Micro Devices- or Intel-based
> servers. The
> > memory limit is 4GB but there are no limits on the size of
> database or
> > number of users.
> >
> 
> this looks good:
> http://www-128.ibm.com/developerworks/db2/library/techarticle/
> 
> can it run on the iSeries? :)
> 
> -Steve
> 
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
> 


------------------------------

message: 3
date: Mon, 30 Jan 2006 22:44:21 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxx>
subject: Re: IFS and CL

Ooooooooh! That's nice!

At 05:50 PM 1/30/2006, you wrote:

>On 30/01/06, James H H Lampert <jamesl@xxxxxxxxxxx> wrote:
> > vhamberg@xxxxxxxxxxx wrote:
> > > You can redirect the output of QShell commands to physical files.
> >
> > Clever! I think you've just put a sword through this particular 
> > Gordian knot.
> >
> > It would be nice if there were a way to put the outfile in QTEMP, 
> > but I suspect that's probably impossible, given that QSHELL runs 
> > across job boundaries. And since I don't expect this thing to be run

> > by multiple users concurrently, it's not a big deal. And at least 
> > for the problem at hand, your solution definitely beats anything 
> > involving third-party downloads or front-ending some API call.
>
>Hi James
>
>No, it's not impossible. Instead of doing the override in QSH, do it in

>the CL first. Using Vern's example:
>
>CRTPF FILE(QTEMP/LS255) RCDLEN(255)
>OVRDBF FILE(STDOUT) TOFILE(QTEMP/LS255) QSH CMD('ls -l /home/vern')
>
>and your output will be in your temporary file. The overrides work fine

>for the 'nix 'standard' files - stdin, stdout & stderr (for use with 
>ftp scripts, et al)
>
>Regards, Martin
>--
>martin@xxxxxxxxxx  AIM/Gaim: DBG400dotNet  http://www.dbg400.net   /"\
>DBG/400 - AS/400 & iSeries Open Source/Free Software utilities     \ /
>Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news   X
>
>--
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
>list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
>unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a

>moment to review the archives at 
>http://archive.midrange.com/midrange-l.



------------------------------

message: 4
date: Mon, 30 Jan 2006 22:47:03 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxx>
subject: RE: Installing only IBMDA400 provider on a server

Not sure if you really need it. All I know is, the install yells at me
when I de-select it. I've not taken the risk of leaving it out yet. Is
it for Navigator? Do you have any experience with leaving it out?

At 07:21 PM 1/30/2006, you wrote:

> >-- Toolbox for Java - must have
>
>Why must you have that? I don't think it's used by the driver, and it's

>an optional part, IIRC.
>
>-Walden
>
>------------
>Walden H Leverich III
>Tech Software
>(516) 627-3800 x3051
>WaldenL@xxxxxxxxxxxxxxx
>http://www.TechSoftInc.com
>
>Quiquid latine dictum sit altum viditur.
>(Whatever is said in Latin seems profound.)
>
>--
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
>list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
>unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a

>moment to review the archives at 
>http://archive.midrange.com/midrange-l.



------------------------------

message: 5
date: Mon, 30 Jan 2006 22:52:33 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxx>
subject: Re: QRY and Dates

Oy! I assumed SQL when the poster said query. Oh, well, the same
techniques pertain, except for result fields, which don't exist in SQL,
and whose expressions need to be written out everywhere they are used.

It's been SOOOOOOO long since I used Query/400!  ;-)

At 06:59 PM 1/30/2006, you wrote:

>I got the following info from a BPCS_L  discussion some time ago.
>* We can only do sub-stringing and concatenation of data in query/400 
>when that data is in the format of alpha field.  We can get numeric 
>there using DIGITS conversion.
>* With the aid of sub-stringing and concatenation, we can get a field 
>into IBM date math format, then from that point we can get # days 
>between current date of running the report to select data that is a few

>days ago, or a few days into the future, or like a range ... from 10 
>days ago to 10 days from now.
>
>     LSDTE is a BPCS numeric field that looks like CCYYMMDD
>     LSDTEA = DIGITS(LSDTE) creating an alpha field from the numeric 
> BPCS field
>     LSDTEAA = SUBSTR(LSDTEA,5,2)||'/'||
>               SUBSTR(LSDTEA.7,2)||'/'||
>               SUBSTR(LSDTEA,3,2)
>               This is now an alpha field that looks like MM/DD/YY
>     LSDTED = DATE(LSDTEAA)
>               This is now a true ISO DATE TYPE for IBM DATE MATH
>               even though it has the // alpha embedded characters
>               which is a nuance of capability Al was unaware of
>               until seeing the BPCS_L discussion of Query/400.
>
>Warning, in BPCS, and possibly other software, the Date field sometimes

>contains data that is not a valid date, such as 99/99/99 and 00/00/00.

>This is not an error, but part of how the BPCS software functions.  
>Having these values in the date field are to tell the BPCS software 
>specific information about the records that contain those values, such 
>as "expired", "inactive", "perfected".
>
>When you are running some software that ASSUMES only valid dates should

>be there, you need to make some provision for do what, if there is data

>there that does not translate into a valid date.  In Query/400 it grabs

>all the data, does the math, then decides what records to select, so if

>your selection criteria is based on calculations of a field that can 
>contain invalid data, your Query/400 can bomb.
>
>It also helps if you know which date fields get this 99/99/99 etc.
>treatment, and which do not.
>
>     LSDTEDYS = DAYS(LSDTED)
>                This gives us days since a distant check point for that

>date (a standard) ... we can then compare this to same calculation 
>against some other date, and get difference in # of days.
>
>    Having done this with several date fields
>    DAYS_DIFF = DAYS(DT_NEW) - DAYS(DT_OLD)
>                such that a positive # is days into the future
>                      and a negative # is days into the past
>
>You can also do this with MONTH or YEAR math.
>
>   YEAR_AGO = CURRENT(DATE) - 1 YEAR
>
>You can extract YEAR MONTH DAY #s but this is not advisable due to 28 
>days in Feb etc. can't do exact days math that way.
>
>   TODAY = CURRENT(DATE)                 Today in mm/dd/yy format
>
>   TOMORROW = DAYS(CURRENT(DATE)) + 1
>              This gives us days count equivalent for day after today
>   Selection criteria
>   LSDTEDYS EQ TOMORROW
>
>   YESTERDAY = DAYS(CURRENT(DATE)) - 1
>              This gives us days equivalent for day before today
>   Selection criteria
>   LSDTEDYS EQ YESTERDAY
>
>   Once you have the CCYYMMDD date converted from numeric, through 
>digits to alpha, so you can sub-string it, then convert to mm/dd/yy 
>date math field, you can do date math to get some # days between that
and CURRENT, which is
>the date you are running the Query/400.    I do this with a lot of
reports
>to get at data that is in the last 7 days, last 10 days, due in the 
>next 2 weeks, and so forth.
>
> >Hi, I've got a file containing dates in yyyymmdd format.  The date 
> >contains entries that are about a year old.  I want to use query, if 
> >possible, to report on records where the dates are the current date 
> >or the current date -1 (yesterday).
> >
> >Does anyone have any examples of how this can be done?
> >
> >Any help appreciated.
> >
> >Thanks
> >--
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
> >mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To 
> >subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> >or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take

> >a moment to review the archives at 
> >http://archive.midrange.com/midrange-l.
>
>
>--
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
>list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
>unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a

>moment to review the archives at 
>http://archive.midrange.com/midrange-l.



------------------------------

message: 6
date: Tue, 31 Jan 2006 09:43:48 +0100
from: "Knezevic, Mihael" <m.knezevic@xxxxxxxx>
subject: RE: SNDNETSPLF not working

thanx for everyone. somehow the msf was not started on one system. after
starting it everything was fine again. (sometimes the solution is so
easy =)

all your help and comments gave me more insight in the os400 operating
system. so thanx to all of you.

mk

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of PaulMmn
> Sent: Tuesday, January 31, 2006 1:51 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: SNDNETSPLF not working
> 
> Even if subsystem QSNADS is up and running on both systems, SNADS can 
> sometimes get hung up.
> 
> Try ending and restarting QSNADS subsystem on both systems.  This 
> normally does not require any special consideration; SNADS is -very- 
> resilient and will pick up where it left off once restarted.
> 
> Also, end and restart MSF  (ENDMSF / STRMSF); end and restart SMTP 
> (ENDTCPSVR  *SMTP / STRTCPSVR  *SMTP).  SMTP  and MSF are used in mail

> distribution; SNADS and MSF and SMTP all tend to get tangled up 
> together.
> 
> Make sure the user profile you're sending to has a directory entry on 
> both the sending -and- receiving systems.
> 
> --Paul E Musselman
> PaulMmn@xxxxxxxxxxxxxxxxxxxx
> --
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
> 
> 



------------------------------

message: 7
date: Tue, 31 Jan 2006 08:18:10 -0500
from: "John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>
subject: RE: CL program

Is this an ILE C program. Do it compile it that way?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, January 30, 2006 5:44 PM
To: Midrange Systems Technical Discussion
Subject: Re: CL program


Why use RTVSYSVAL instead of CEELOCT?  Seems like CEELOCT would be
shorter than RTVSYSVAL followed by CEEDAYS -- plus, the way you're doing
it assumes that the system value is in MMDDYY format, which it may not
be. So your code would be shorter and more correct using CEELOCT.

Also, if you supply a feedback code (&FC) you should check it to see if
the API failed.  If you don't want to do any checking, pass *OMIT so
that the operating system's default error handling mechanish can kick
in.

(I just posted an example very similar to yours, but uses CEELOCT)

> pgm
> DCL &DATE *CHAR 6
> DCL &LILDATE *CHAR 4
> DCL &FC *CHAR 12
> dcl &monthyear *char 7
> /* get system date */
> rtvsysval qdate &date
> /* change to first of month */
> CHGVAR &DATE (%SST(&DATE 1 2) *CAT '01' *CAT %SST(&DATE 5 2))
> /* get "lillian" date number */
> CALLprc CEEDAYS (&DATE 'MMDDYY' &lildate &fc)
> /* subtract 1 day to get last day of previous month */ CHGVAR 
> (%BIN(&LILDATE)) ((%BIN(&LILDATE) - 1))
> /* get 3-char month name + 4-digit year */ CALLprc CEEDATE (&lildate  
> 'MMMYYYY'  &monthyear  &fc) endpgm

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



------------------------------

message: 8
date: Tue, 31 Jan 2006 07:23:20 -0600
from: Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx>
subject: Re: CL program

You can add a job schedule entry to run your CL program on the last day 
of the

ADDJOBSCDE CMD(CALL MYPROGRAM FRQ(*MONTHLY) SCDDATE(*MONTHEND)

That will eliminate any need to compute the last day of the month in 
your program.  All you would then do is retrieve the month in your 
program and convert it to character to use in your library name.

Incidentally, you might be better served by naming the libraries with a 
common alphabetic prefix and then the date in YYYYMM format. Then you 
wouldn't even have to convert the month to character and, in addition, 
when you work with the libraries from a command line they will display 
in sorted order.

John Candidi wrote:
> Let me describe what I'm trying to do. I'm sure it's pretty simple for
> anyone who knows CL.
> 
>  
> 
> I need to create a library with the month-end name (i.e. after January
> month-end, I'd need a JAN2006 library) that will contain 10 files
which I
> copy into it. I will need to do this every month as part of our
month-end
> process. I assume it will have to subtract several days from today's
date
> and pull the month and year from that date in case month-end is not
run on
> the last day of the month Is there a simple CL program to do this.
> 
>  
> 
> John A Candidi
> 
> Rutgers Insurance Companies
> 
> IT Director - AS/400 Manager
> 
> 856-779-2274
> 
>  
> 
>  
> 



------------------------------

message: 9
date: Tue, 31 Jan 2006 06:33:17 -0700
from: michael@xxxxxxxxxxxxxxxxxx
subject: RE: CL program

That is an ILE CL program. Create it with CRTBNDCL, or option 14 from
PDM with a CLLE source type.

> -------- Original Message --------
> Subject: RE: CL program
> From: "John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>
> Date: Tue, January 31, 2006 8:18 am
> To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
> 
> Is this an ILE C program. Do it compile it that way?
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Monday, January 30, 2006 5:44 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: CL program
> 
> 
> Why use RTVSYSVAL instead of CEELOCT?  Seems like CEELOCT would be
shorter 
> than RTVSYSVAL followed by CEEDAYS -- plus, the way you're doing it 
> assumes that the system value is in MMDDYY format, which it may not
be. So 
> your code would be shorter and more correct using CEELOCT.
> 
> Also, if you supply a feedback code (&FC) you should check it to see
if 
> the API failed.  If you don't want to do any checking, pass *OMIT so
that 
> the operating system's default error handling mechanish can kick in.
> 
> (I just posted an example very similar to yours, but uses CEELOCT)
> 
> > pgm
> > DCL &DATE *CHAR 6
> > DCL &LILDATE *CHAR 4
> > DCL &FC *CHAR 12
> > dcl &monthyear *char 7
> > /* get system date */
> > rtvsysval qdate &date
> > /* change to first of month */
> > CHGVAR &DATE (%SST(&DATE 1 2) *CAT '01' *CAT %SST(&DATE 5 2))
> > /* get "lillian" date number */
> > CALLprc CEEDAYS (&DATE 'MMDDYY' &lildate &fc)
> > /* subtract 1 day to get last day of previous month */
> > CHGVAR (%BIN(&LILDATE)) ((%BIN(&LILDATE) - 1))
> > /* get 3-char month name + 4-digit year */
> > CALLprc CEEDATE (&lildate  'MMMYYYY'  &monthyear  &fc)
> > endpgm
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.



------------------------------