RE: Test Envirnoment -- SYSTEM21

We only duplicated the objects that we needed to.  Rather than creating a
bunch of new libraries for each environment (and then adding them all to the
library lists which were maxing out in space already), we placed all of
these objects for the environment in a single library called something like
OSLTEST or OSLDEV (We had both for a while).

You will need to add this library to each library list in the environment.

The alternative is to make copies of all the libraries and rename all the
libraries in all the library lists and job descriptions.  This seems like
more work, and will require a lot more DASD to house.


-----Original Message-----
From: Diana Larsson [mailto:dlarsson@xxxxxxxxxxxxxxxxxx] 
Sent: Monday, July 12, 2004 2:20 PM
To: 'System 21 Users'
Subject: RE: [SYSTEM21] Test Envirnoment


Did you create new D3, P3 libraries as well? Or did you just create the job
descriptions in a custom library Example job description CSBACK3 resides in
OSLCSD3  duplicate the job description to TSTCSBACK3 in library ?????/

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx]
On Behalf Of Lemon, Michael
Sent: Monday, July 12, 2004 1:51 PM
To: 'System 21 Users'
Subject: RE: [SYSTEM21] Test Envirnoment

Diana,

We've had a test/development environment for the 8+ years that we've used
System/21 and its predecessor and have liked everything about it except that
they share a common application allocation system (When you run a task that
requires exclusive use of a module in test, your users in the live
environment are also locked out).  This can be frustrating at times, and was
the one benefit of having a world that we liked.

Here are some of the things that I remember doing when setting up the test
environment:

- Create test data libraries to mimic your live environment.  In our case we
have consolidated to a single data library called something like JBADATA in
Live and JBADATATST in our test environment.  Make sure you duplicate all
the objects in the library (including the data queues, data areas, and job
descriptions where applicable)
- Create duplicate subsystem descriptions for the JBA subsystems.  We
renamed our duplicates with postfix TST (INBACK3 -> INBACK3TST)
- Duplicate the job descriptions and change the library list on them to
reflect your test environment data and modification libraries.- Set up your
applications for the test environment
- Create duplicate library lists from your Live applications into your test
applications, and rename the live data file library to be the test
equivalent.
- Add your test modification library (if you have one) to all the library
lists mentioned above.  You will want to place it before your live
modification library (if you have one).
- I remember having to tweak something to get ALL the background jobs to
work correctly.  I don't quite remember what it was though.  I'm sure the
subsystem name is hard coded somewhere in a couple of the modules, so you
will have to modify these programs to refer to your new subsystems.

Take the above with a grain of salt... I last did this about 6 years ago.

-Mike



-----Original Message-----
From: Diana Larsson [mailto:dlarsson@xxxxxxxxxxxxxxxxxx]
Sent: Monday, July 12, 2004 1:23 PM
To: 'System 21 Users'
Subject: [SYSTEM21] Test Envirnoment


 

I am looking for some help/verification on setting up a test environment. We
are presently using worlds and need to convert to environments. We plan to
use it for testing and development. Any help would be much appreciate online
or offline. Thanks 
Diana



 ARDEN COMPANIES
                 A Global Company
                   1964--2004   
Celebrating 40 years of making your life more comfortable! 

This message may contain confidential and/or privileged information.  If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein.  If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message. Thank
you for your cooperation.

This OUTBOUND document has been scanned by an Antivirus Server. 

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.



This INBOUND document has been scanned by an Antivirus Server. 




 ARDEN COMPANIES
                 A Global Company
                   1964--2004   
Celebrating 40 years of making your life more comfortable! 

This message may contain confidential and/or privileged information.  If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein.  If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message. Thank
you for your cooperation.

This OUTBOUND document has been scanned by an Antivirus Server. 

_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.