Joined: 02 Dec 2002 Posts: 629 Topics: 176 Location: Stockholm, Sweden
Posted: Thu Jul 20, 2023 4:48 am Post subject: Excluding IMS segments using File Manager IMS in batch
If I run FMI via the standard panels, and I've defined a view for the database, then that view (I think) allows me to exclude which segments are shown on the resulting browse of the database.
For example, when I'm presented with a list of the segments (say 1-5), I can place an X next to segment numbers 2-4 and the resulting browse panel will only show me segments 1 & 5.
Is there a way to do this in FMI batch using IXB? If so, what is/are the parameter(s) I need to use. (if you don't know what the relevant parameter is called it's a bit difficult to know what to search for). _________________ Michael
Joined: 02 Dec 2002 Posts: 629 Topics: 176 Location: Stockholm, Sweden
Posted: Wed Jul 26, 2023 5:08 am Post subject:
Okay, reviewing the manual and parms for IXB it seems there is no VIEW option.
Having said that, if that IS true, I'm surprised I don't receive an error message.
The IXB doc in the manual clearly states
Quote:
This function extracts all segments or selected segments from a database
which based on the PF1 help indicates (for me) that only segments SFLIV and SFBETH are selected as the segments to be extracted.
And yet the results from the submitted JCL with the FMIMSIN parms still extracted all segments. _________________ Michael
My bad, but it seems that duplicate key words result in the only the first one being used and any duplicates being discarded
(with no warning that I could see).
The final solution that resulted in what I was after was the following
where my criteria definition "defined" the fact that I only wanted 2 of the segments unloaded and none of the other ones.
(and this obviously assumes you have defined the criteria via FMI)
I use this JCL as a way of unloading all/specific segments from a DL/1 database
A Rexx script then reads the unloaded file and compares the segment contents against equivalent, replacement DB2
tables (we're converting DL/1 databases to DB2 ones).
The idea being that we can see immediately if a specific key's contents differ after program updates to both
DL/1 and DB2. _________________ Michael
My bad, but it seems that duplicate key words result in the only the first one being used and any duplicates being discarded
(with no warning that I could see).
The final solution that resulted in what I was after was the following
where my criteria definition "defined" the fact that I only wanted 2 of the segments unloaded and none of the other ones.
(and this obviously assumes you have defined the criteria via FMI)
I use this JCL as a way of unloading all/specific segments from a DL/1 database
A Rexx script then reads the unloaded file and compares the segment contents against equivalent, replacement DB2
tables (we're converting DL/1 databases to DB2 ones).
The idea being that we can see immediately if a specific key's contents differ after program updates to both
DL/1 and DB2. _________________ Michael
My bad, but it seems that duplicate key words result in the only the first one being used and any duplicates being discarded
(with no warning that I could see).
The final solution that resulted in what I was after was the following
where my criteria definition "defined" the fact that I only wanted 2 of the segments unloaded and none of the other ones.
(and this obviously assumes you have defined the criteria via FMI)
I use this JCL as a way of unloading all/specific segments from a DL/1 database
A Rexx script then reads the unloaded file and compares the segment contents against equivalent, replacement DB2
tables (we're converting DL/1 databases to DB2 ones).
The idea being that we can see immediately if a specific key's contents differ after program updates to both
DL/1 and DB2. _________________ Michael
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum