Hi Evan and Al,

Thanks for replying.

The main thing for using iasp'S would be to keep our developers from touching data on the other asp. The main idea is to create some sort of lpar envioronment without the lpar overhead and costs.

What time frame are we looking at if we want to create this setup.

Currently we have a lot of jobdescriptions, susbsystems, hardcoded library names and so on. However, we are currently in the process of cleaning up al qualified things.

Thanks again for replying.

Best Regards,

Wim Jongman






Evan Harris wrote:


Hi Wim

I forgot to mention:

the original HTTP server does not support access to IASP's so if your doing eRPG on the original HTTP server you will need to have your programs in *SYSBAS and update them to include a SETASPGRP command in their *INZSR or similar so they can get to the data out in the IASP.

Cheers
Evan Harris


Hi All,

We want to create a mirrored machine with Vision and we want to develop on this machine. However, for the development machine we need some production libraries to compile and test against that are also on the the production machine.

We want to create the libraries with the same name but in different IASP's.

I have read some of the older threads, but I wonder if there are any new insights. What needs to be changed the most if we take the IASP approach?

Best regards,

Wim


_______________________________________________
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-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.