Sent from Yahoo Mail for iPad
On Thursday, May 23, 2024, 2:29 AM, ITschak Mugzach
<05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
All major relational databases support variable length data load (incl.
DB2) . This is not a problem at all.
ITschak Mugzach
*|** IronSphere Platform* *|*
All major relational databases support variable length data load (incl.
DB2) . This is not a problem at all.
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
On Wed, May 22, 2024 at 11:41 PM Tom Ross
>On Tue, 21 May 2024 15:01:12 + "Schmitt, Michael"
> wrote:
>
>:>3. Depends on the language. IMS can have variable length segments but not=
> variable length fields, so any variable length fields are defined by the a=
>pplication. If the application is in COBOL, there's no native variable
01 segment.record.
05 name1-length pic s9(04) comp.
05 name2-length pic s9(04) comp.
05 name3-length pic s9(04) comp.
05 name4-length pic s9(04) comp.
05 name5-length pic s9(04) comp.
05 name1-text.
10 name1-char pic x(01) occurs 0 to 99 times depending on name1-length.
05 name2-text.
10
All thength fields MUST occur before length depending on.
On Tue, May 21, 2024 at 10:23 AM Binyamin Dissen
wrote:
>
> On Tue, 21 May 2024 15:01:12 + "Schmitt, Michael"
> wrote:
>
> :>3. Depends on the language. IMS can have variable length segments but not
> variable length fields, so any
One thing that I haven't seen mentioned is that converting from EBCDIC to UTF-8
is that some characters in UTF-8 are 2 or 4 bytes, thus changing the lengths of
fields.
--
Tom Marchant
On Tue, 21 May 2024 04:08:16 -0500, Jason Cai wrote:
...
> We have all the necessary copybooks and are
But the location of the ODO length is application dependent. It might even be a
calculated field in working storage. It isn't like there's a defined field type:
"Var-length field is binary fullword length followed by a stream of bytes where
the length of the stream is the fullword length, not
On Tue, 21 May 2024 15:01:12 + "Schmitt, Michael"
wrote:
:>3. Depends on the language. IMS can have variable length segments but not
variable length fields, so any variable length fields are defined by the
application. If the application is in COBOL, there's no native variable length
Arrgh, meant to type that unload from image copy restores to a DATASPACE, i.e.
in memory. But my point is it requires an IMS system.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Schmitt, Michael
Sent: Tuesday, May 21, 2024 10:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Some others have answered your questions, but here's my $0.02 USD:
1. You should convert all the numeric fields to edited text. Otherwise, unless
you're using a COBOL system on Linux, you'll have trouble with the field
formats. Think packed decimal, implicit signs, little/big endian, etc.
2.
Each segment must be its own table with the combined key that includes
the key of the parent in parent order.
On Tue, May 21, 2024 at 6:56 AM Binyamin Dissen
wrote:
>
> On Tue, 21 May 2024 04:08:16 -0500 Jason Cai wrote:
>
> :>In the IMS system I work on, 99% of the segment fields are not
On Tue, 21 May 2024 04:08:16 -0500 Jason Cai wrote:
:>In the IMS system I work on, 99% of the segment fields are not defined in the
DBD.
>From my IMS recollection, that is typical. The application code has maps of
the segments. Only fields used in searches needed to be defined.
So if you
Jason and all,
Attila words are wise, but there is more.
From your email, I'm not certain if you are talking about one data base
or a collection of data bases.
It's good that you have an image copy (copies) and apparently the DBDs,
but there is more to it.
Do you know if your data bases
Jason, your applications will be in for a big surprise if you follow this
conversion path.
For example, PIC 9(4) COMP is a binary numeric field which is BIG ENDIAN on
mainframe, most (but not all) LUW and cloud systems are LITTLE ENDIAN. So
you need to convert these fields, otherwise the numbers
json,
You can process the unload file if you know the record format. This, the
record format, depends on the utility used to perform the unload. Once you
have it, map the segment name to segment layout from the copybook. If you
have easyTrieve installed, you can convert the copybooks to offset
Dear Micael and all
Thank you very much for your response and the valuable information provided.
Over the past few days, I discussed the DBD definitions with our IMS DBA, and
we have a similar setup
where “The only fields that are required to be defined in a DBD are the keys,
indexed
16 matches
Mail list logo
