RE: Use of the IFS

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 02, 2009 8:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Use of the IFS

By golly John I think you understand perfectly!

A "trigger" is a legitimate term used in DB2 on the i. That
could update
the IFS file. Then the PC app could read that. No refresh
needed. You
just change the default data directory from something like
c:\BubbasApp\data
to
x:\BubbasApp\data
where x is a drive mapped to a "share" defined on the i

For those who haven't yet dabbled into updating IFS files
directly you
could also do this:
ADDLNK OBJ('/qsys.lib/rob.lib/noddspf.file/noddspf.mbr')
NEWLNK('/rob/noddspf.txt')

and then this works fine
dspf '/rob/noddspf.txt'

When I opened it up in Notepad it looked like garbage though.
hmm,
CRTPF FILE(ROB/noddspF) RCDLEN(75)
was how it was created.
and, even though system value QCCSID is set to 37 it had picked 65535.
Oh, that's right - no dds and no sql (ie RCDLEN parameter used) WILL
result in 65535.
STRSQL
CREATE TABLE ROB/NODDSPF
(ONEFIELD CHAR (75 ) NOT NULL WITH DEFAULT)
RCDFMT NODDSPFR
The CCSID of the file, and the field, are now 37.
INSERT INTO ROB/NODDSPF VALUES('Live and let live.')
Still looks like crud in Notepad.


Rob Berendt
--

Your problem is most likely due to the file on the "i" being in EBCDIC
whereas notepad on the PC wants ASCII with CRLF line endings. This means
that the DB2 trigger would need to translate the data from EBCDIC to
ASCII and append an CRLF (0x0d 0x0a) to the end of each logical line.

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)
Administrative Services Group
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john.mckown@xxxxxxxxxxxxxxxxx * www.HealthMarkets.com

Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.