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



The QSYSVxRyMz libraries are not intended for actual use, but rather for
compilation purposes to prior releases.  To compile/restore to V4R4M0, you
should use the regular QSYS  commands with the parameter TGTRLS(V4R4M0).

>From V5R1, you can only go back to V4R4, but from V4R5 and lower you can go
to any RISC release by specifying TGTRLS(V3R2M0).  This likely will bring
on some undue overhead, because reencapsulation will be required on the
restore, even to another RISC release

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    "McCallion, Martin"
                    <martin.mccallion@m       To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    isys.com>                 cc:
                    Sent by:                  Subject:     RE: Target release 
behaving strangely on saves from V5R1
                    midrange-l-admin@mi
                    drange.com


                    02/08/02 04:31 AM
                    Please respond to
                    midrange-l






Arlen Nissan wrote:

> Do you have various release libraries???   Why don't you try
> using the Savf
> cmd from the level you want???

Thanks, Arlen, it was a good idea.  Unfortunately, when I prompted
QSYSV4R4M0/SAVLIB I got message CPD0118: "Command SAVLIB not valid for
current release."

It goes on to say that those commands are only there for compiling CL
programs with specified target release values.  But it was worth a try.

I got around my immediate problem by restoring on a V4R5 machine and
re-saving, but it does seem that there's a bug.

Cheers,

Martin.

--
Martin McCallion
Senior Technical Consultant
Work:  martin.mccallion@misys.com
Home: martin.mccallion@ukonline.co.uk
Misys International Banking Systems
1 St George's Road, London, SW19 4DR, UK
T +44 (0)20 8486 1951
F +44 (0) 20 8947 3373
www.misys.com
This email message is intended for the named recipient only. It may be
privileged and/or confidential. If you are not the  intended named
recipient of this email then you should not  copy it or use it for any
purpose, nor disclose its contents to any other person. You should
contact Misys International Banking Systems as shown below so that we
can take appropriate action at no cost to yourself.
Misys International Banking Systems Ltd,1 St
George's Road, London, SW19 4DR, UK. Email: ibs.postmaster@misys.com.
Tel: +44 (0) 20 8879 1188 Fax: +44 (0) 20 8947 3373
Misys International Banking Systems Ltd is
registered in England and Wales under company no. 971479

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
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.