|
Good man Dean, You're right. Yesterday, I duplicate all BOM500D1 records in ZOP file for my new program and it works. Thx all for your help. Oludare ----- Original Message ----- From: "Genyphyr Novak" <novakg@ssax.com> To: <BPCS-L@midrange.com> Sent: Thursday, March 09, 2000 5:44 PM Subject: Re: Modification to ASSET program BOM500D1, BOM500D4 > Hi Dean, > > I think this is what you were talking about ? The ZKY file holds the user > preferences for remembered keys, so should not have anything to do with > security. I am not sure if this SCOPE entry covers every single step > required, but it is an outline of what is required to add a new program to > use group security features of the function key group security. So, also > Oludare has to add his new program/key literals to the ZOP file, not just > the BPCS Security Objects files. BOM500D1 does use the calls to the programs > which search this additional security file. You would have to copy all the > entries for BOM500D1 to be also entries under the new program name. Here are > the entries for BOM500D1, for example: > > ....+....1....+....2....+....3....+....4....+....5....+....6....+. > Rec WEPALG Seq Msg ID Requisitioner Date 8,0 DHEXTM > Id No I.D. > OP BOM500D1 L032358 SSA 19,960,829 50000 > OP BOM500D1 1 L009416 SSA 19,960,829 50000 > OP BOM500D1 2 L018172 SSA 19,960,829 50000 > OP BOM500D1 3 L019081 SSA 19,960,829 50000 > OP BOM500D1 4 L018174 SSA 19,960,829 50000 > OP BOM500D1 5 L018178 SSA 19,960,829 50000 > OP BOM500D1 6 L019082 SSA 19,960,829 50000 > OP BOM500D1 8 L018004 SSA 19,960,829 50000 > OP BOM500D1 12 L032142 SSA 19,960,829 50000 > OP BOM500D1 13 L032458 SSA 19,960,829 50000 > OP BOM500D1 14 L032011 SSA 19,960,829 50000 > OP BOM500D1 16 L032060 SSA 19,960,829 50000 > OP BOM500D1 113 L019083 SSA 19,960,829 50000 > OP BOM500D1 114 L032034 SSA 19,960,829 50000 > > > From SCOPE: > > > Platform: A400 > Product: SYS > Version: 6.004 > Program: SYS603 > Closed Date: 1998-08-10 > Closed By: NOVAKG > Incident #: 553571 -1 > > Group Security - How do you add programs to this? Also, how can you tell if > a program is enabled to use this function? Not all programs are listed when > I want to change settings in Group Security (SYS603D). I want to be able to > make all my BPCS programs authorized by functions like this. > > Not all BPCS programs contain the functionality to have specific functions > authorized or not. To tell if a product should be able to work in SYS603, > you can view the source. Within the AOBLFK subroutine, it should call > SYS007B2, rather than SYS007B to allow only function keys that are > authorized to the user to appear on the screen. In the AOBLAC subroutine, > the program should call SYS006B2, rather than SYS006B so that only the > action commands the user is authorized to modify will appear. If the program > does do this, but is missing from SYS603, you would use a database utility > to add a record to the ZOP file setting OPID to 'OP', OPPROG for the program > name, OPSEQ as the option number (sequence number) and OPDESC as the message > ID associated with the option. If the product in question does not call the > required security programs, then the user would have to modify BPCS. Several > Enhancement BMRs exist to add more BPCS programs to SYS603. > > Thanks > Genyphyr Novak > SSA > > -----Original Message----- > From: DAsmussen@aol.com <DAsmussen@aol.com> > To: BPCS-L@midrange.com <BPCS-L@midrange.com> > Date: Thursday, March 09, 2000 3:05 PM > Subject: Re: Modification to ASSET program BOM500D1, BOM500D4 > > > >Dare, > > > >In a message dated 3/9/00 12:26:40 PM Eastern Standard Time, > >oludare@ix.netcom.com writes: > > > ><<snip>> > >> I HAVE MADE SOME MODIFICATIONS TO BOM500D1 AND COMPILED WITHIN ASSET. > The > >> problem is I can not get the program to work correctly. The program > >initial > >> response time is extremely slow (about 10-20min), all action items are > >> missing except for "8=Position to" and items descriptions are not > showing.. > >> The program names are changed to BOM50DD1=*DSPF, BOM50DDR=*RPG, > >BOM50DDC=*CLP, > >> CLMSGD=*MSGF during interractive compilation. > ><<snip>> > > > >You forgot the "numero uno" rule for technical questions here -- state your > >release and platform. However, I can infer from your problem that you are > on > >the AS/400 (no ADK on the HP, AFAIK), mixed mode (can't modify display > >programs on full client) and that you are on at least 6.something. Your > >renaming of the objects was the problem. Why did you not keep the original > >names and place the objects in BPCSUSR (which is SOP for modifying BPCS)? > >BOM500 is one of the programs that incorporates function key and action > code > >level security. If you rename it, the function keys and action codes will > >not be authorized to group SSA (or whatever group you're using). To my > >knowledge, SSA's program to maintain this authority _STILL_ doesn't allow > you > >to add new programs to the list, so using DBU or DFU on the (ZKY?) file is > >the only way to fix your problem other than renaming the programs to their > >proper names. Name the programs back to their originals, or check out the > >security program for which file needs to be modified... > > > >HTH, > > > >Dean Asmussen > >Enterprise Systems Consulting, Inc. > >Fuquay-Varina, NC USA > >E-mail: DAsmussen@aol.com > > > >"Success is getting what you want. Happiness is liking what you get." -- > H. > >Jackson Brown > >+--- > > > +--- > | 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.