|
You can use an older ADK to browse the action diagrams. You may lose some enhancements if you use the older ADK to compile them, however, If you read the ADK Net Changes for 6.1.00 you will see some important changes were made in that release of the tool that change the way SQL is used and the way programs compile and the way that CLMSG compiles. So, you should use 6.1.00 ADK to update 6.1.00. Certain programs may not work the same if 6.0.04 ADK is used to compile them, particularly for performance considerations. While it is unlikely a 6.1.00 BPCS program will stop working completely if compiled in 6.0.04 ADK, this scenario is not tested by SSA. At SSA 6.1.00 ADK is used to make 6.1.00 BPCS and other versions of ADK are not tested to compile the new release. Both ADK releases can co-exist on the same box, and do here at SSA on at least 3 different boxes. However there are no written instructions on how to do this per se. You can simply install 6.1.00 ADK as a new version on your system rather than asking the install to update your existing ADK 6.0.04 if you are going to want both versions of ADK on the box. Be sure to read the instructions for installing ADK 6.1.00 carefully. An issue exists described by the below BMR - so ensure your Control and Object library both have the same name, such as ASSETO61 : MR Number: 49981 Priority Code: A Version Reported: 6100 Platform Reported: AS400 Program: INS Origin Code: I Completed Date: 00-00-00 Rejected Date: 00-00-00 Rejected Reason: INSTADK allows wrong lib names When using INSTADK and installing the ADK tool, the install program allows the user to enter seperate names for the Control and Object library. The default name for both of these is 'ASSETO'. These must be the same name, or the environment which installs will be invalid. Instead, the install program should not prompt the user for 2 names - it should prompt for one name, and name both libraries the same thing to avoid program errors later. Instructions for installing ASSET were updated to warn users of this, but for future, the install program should not allow users to enter invalid options for these names. When loading the 6.1.00 repository into ADK 6100, be aware of this MR, and if necessary you can temporarily rename some libraries on your system to get through the install of the repository, then change the library name back to what you wanted it to be. MR Number: 49982 Priority Code: A Version Reported: 6100 Platform Reported: AS400 Program: INS Origin Code: I Completed Date: 00-00-00 Rejected Date: 00-00-00 Rejected Reason: Repository hardcodes ASSETSAVE Install program for the BPCS AS/SET repository hard-codes an assumed value of ASSETSAVE as the name of the library where ASSET will retrieve the repository programs to built a set during save/restore operations. However, when a user installs ASSET, they are allowed to call this library whatever they choose to. The repository install should allow the user to specify the name of their ASSETSAVE library, in the case that they have named it other than the default value. For now, instructions have been altered to warn users when installing ADK that the BPCS repository will expect the library 'ASSETSAVE'. For future, repository install should allow a different name. -----Original Message----- From: Kevin_Catlin@GM.cytec.com <Kevin_Catlin@GM.cytec.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Wednesday, January 12, 2000 3:51 PM Subject: Re[2]: AS/SET Versions in use at SSA Genyphyr Am I to infer from the previous posts in this thread that you MUST use 6.1.00 ADK to browse/modify 6.1.00 BPCS Action Diagrams? Is it possible to have 6.0.04 ADK and 6.1.00 ADK co-existent on the same box? Kevin Catlin CYTEC Industries kevin_catlin@gm.cytec.com ______________________________ Reply Separator _________________________________ Subject: Re: AS/SET Versions in use at SSA Author: BPCS-L@midrange.com at Internet Date: 01/12/2000 12:42 PM Actually you need to use version 6.0.04 ADK, not 6.1.00. Version 6.1.00 has not been tested at SSA to generate 6.0.02 BPCS. Because of this, it is recommended by R&D at SSA that you use 6.0.04 ADK with all releases of BPCS below 6.1.00. This is available on CISC or RISC. When you install the new release, it prompts you for an existing environment of ADK and will automatically upgrade the release and do any required changes to the ADK files. Thanks Genyphyr Novak SSA -----Original Message----- From: Mark Bazer <mbazer@dynomerch.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Wednesday, January 12, 2000 8:18 AM Subject: RE: AS/SET Versions in use at SSA Is AS/SET version 6.0.02 Y2K compliant. If not, what do we have to do to make it so? Thanks, Mark Bazer Dyno Merchandise -----Original Message----- From: Genyphyr Novak [mailto:novakg@ssax.com] Sent: Tuesday, January 11, 2000 4:22 PM To: BPCS-L@midrange.com Subject: Re: AS/SET Versions in use at SSA SSA is using 6.0.04 AS/SET for releases lower than 6.1.00 (BPCS CD, 6.0.02 and 6.0.04) and for BPCS 6.1.00 are using 6.1.00 ADK. We have the Y2K fixes applied. Thanks Genyphyr Novak SSA -----Original Message----- From: MacWheel99@aol.com <MacWheel99@aol.com> To: BPCS-L@midrange.com <BPCS-L@midrange.com> Date: Monday, January 10, 2000 2:11 PM Subject: Re: Y2K bug - ASSET problem with %CMD > The only solution I could find for this, is to upgrade to version 6 of > ASSET. That version is Y2K compliant. What version is SSA using for BMRs sent us? Al Macintyre c¿c +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
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.