× 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 wouldn't hold your breath that the follow on to V5R3 has a like ptf. 
Normally these kind of temporary work arounds are only good for one 
release to convince people that IBM was serious when they put that stuff 
in the Memo to Users.  Another reason not to skip releases.  You loose the 
chance to see this kind of stuff.

You see it on this list, you read it in the Memo to Users, however you 
don't really think IBM would make a change that drastic that stops your 
applications from working until it actually happens to you.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/30/2005 06:46 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: CPYFRMIMPF and double delimiters






V5R3 changed the way the CPYFRMIMPF works.  This was documented in the 
release notes for V5R3.  Just recently IBM announced a PTF that lets you 
go back to the original functioning of the command.  The PTF is SI17635.

Tom Liotta wrote:
> midrange-l-request@xxxxxxxxxxxx wrote:
> 
> 
>>  2. Re: CPYFRMIMPF and double delimiters (daparnin@xxxxxxxxxxxxxx)
>>
>>Interesting...  I tried this, first on our V5R1 system and got this:
>>
>>....+....1....+....2....+....3....+....4....+.
>>MYTEXT                                  MYNBR
>>1 1/2                                       1
>>********  End of data  ********
>>
>>Next, I tried it on our V5R3 system and got this:
>>....+....1....+....2....+....3....+....4....+.
>>MYTEXT                                  MYNBR
>>1 1/2"" of stuff                            1
>>********  End of data  ********
>>
>>I copied and pasted the commands from one screen to another.  Both 
systems
>>got the latest PTF's in January so they shouldn't be too far off.
> 
> 
> 
> Keep in mind that "latest PTFs" is not the same as "latest cumulative 
PTF package". Did you mean you have installed the latest cumes?
> 
> There may be any number of relevant PTFs that are not on any cume 
package and never will be on a cume package. These PTFs must be ordered 
individually if you need them. Sometimes they provide new features; 
sometimes they handle situations that are relevant or needed only by a 
relatively few customers.
> 
> It may be that IBM decides to include them in a cume package only after 
a sufficient number of customers ask for them. I don't know if IBM has 
ever explicitly stated what criteria determines whether one goes on a 
cume.
> 
> Tom Liotta
> 
> 

-- 
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.