I resolved the issue, I had to change the sassys and ssasys2
Dataarara's and copy some control files.
Thanks for your help....... 

Michael De Gennaro


-----Original Message-----
From: bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx] On Behalf Of
Clare Holtham
Sent: Saturday, July 23, 2005 2:21 AM
To: SSA's BPCS ERP System
Subject: Re: [BPCS-L] BPCS test system

No, I don't think it's a key problem. More likely to be that he hasn't
followed the correct procedure in setting up a new BPCS environment on
the
same box (data areas etc) and it isn't setting up the LDA correctly and
so
he's getting a security violation...

cheers,

Clare

----- Original Message ----- 
From: <fwsoftware@xxxxxxx>
To: <bpcs-l@xxxxxxxxxxxx>
Sent: Friday, July 22, 2005 4:02 PM
Subject: Re: [BPCS-L] BPCS test system


> Mike,
>
> If this new test environment is on a different box (serial number
change)
sounds like you wiped out the BPCS key data area.
>
> Dave Trevino
> Framework iSystems
>
>
> -----Original Message-----
> From: Michael DeGennaro <miked@xxxxxxxxxxxxxx>
> To: SSA's BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
> Sent: Fri, 22 Jul 2005 09:54:40 -0400
> Subject: RE: [BPCS-L] BPCS test system
>
>
> Sev       Type    Text                    Program
>  30        DIAG    Message not sent. ACP29 QMHSNBRK
>                    0B in *LIBL not work st
>                    ation message queue.
>  40        ESC     Error occurred when sen QMHSNBRK
>                    ding message.
>  40        ESC     Function check. CPF2469 QMHUNMSG
>                     unmonitored by SYS656C
>                    C at statement *N, inst
>                    ruction X'003C'.
>                              Variables
>
>
> Also
> Call IIT031E
> Cannot resolve to object NWICSTUB *pgm not found
> Sndbrkmsg  ('security violation') tomsgq(SSATCP) SSATCP not work
station
> message queue not sent.....
>
> Michael De Gennaro
>
>
> -----Original Message-----
> From: bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx
> [mailto:bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx] On Behalf Of
> Jim Mergen
> Sent: Friday, July 22, 2005 9:48 AM
> To: SSA's BPCS ERP System
> Subject: RE: [BPCS-L] BPCS test system
>
> What is the message you are receiving?
>
> -----Original Message-----
> From: bpcs-l-bounces+jmergen=pctcnet.net@xxxxxxxxxxxx
> [mailto:bpcs-l-bounces+jmergen=pctcnet.net@xxxxxxxxxxxx]On Behalf Of
> Michael DeGennaro
> Sent: Friday, July 22, 2005 8:38 AM
> To: SSA's BPCS ERP System
> Subject: RE: [BPCS-L] BPCS test system
>
>
> I created a duplicate object of the BPCSF604 library
> To testf604 and copied the files ZSC,ZXM,ZXO,ZXP,ZXU and ZMA from a
copy
> of my old test data, that was working.
>
> I get a security violation when a try to run anything.
> Is there something missing like a dataara etc????
>
> Thanks
> Michael De Gennaro
>
>
> -----Original Message-----
> From: bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx
> [mailto:bpcs-l-bounces+miked=teltronics.com@xxxxxxxxxxxx] On Behalf Of
> Dan Sweeney
> Sent: Thursday, July 14, 2005 9:17 PM
> To: 'SSA's BPCS ERP System'
> Subject: RE: [BPCS-L] BPCS test system
>
> I disagree SSASYS and SSASYS2 data areas are in the files library and
> not the object library. You are correct you did over simplify the
issue.
>
> -----Original Message-----
> From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx
> [mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On
Behalf
> Of Steve Segerstrom
> Sent: Thursday, July 14, 2005 6:42 PM
> To: SSA's BPCS ERP System
> Subject: RE: [BPCS-L] bpcs test system
>
> We are bpcs 6.04.
>
> We have a pretty straightforward set-up and this is probably an
> oversimplification. SO WARNING -  there may be other issues that you
> have that we would not.
>
> For us we have two data libraries (Native BPCS and our customer
files).
> We ONLY restore these data libraries; with the exception of these
files:
>
>     ZSC ZXM ZXO ZXP ZXU ZMA
> This comes with a cost ; occasionally folks put something in these
files
> in production and don't have the same entries in test system
>
> Source moves from our test to production so we don't move programs.
>
> We use the same data areas in production as in test.
>
> Data areas for BPCS are in our program libraries.
>
> The only real problems we have had is if someone has a test file not
> promoted (they have to set up the file again) or if they have not
> promoted a sys105 table (it will be lost). We announce the move loudly
> and clearly and really only do several per year.
>
> -----Original Message-----
> From: bpcs-l-bounces+ssegerstrom=intermatic.com@xxxxxxxxxxxx
> [mailto:bpcs-l-bounces+ssegerstrom=intermatic.com@xxxxxxxxxxxx]On
Behalf
> Of Michael DeGennaro
> Sent: Thursday, July 14, 2005 3:47 PM
> To: bpcs-l@xxxxxxxxxxxx
> Subject: [BPCS-L] bpcs test system
>
>
> Does anybody know how to move production files
> To a test environment with out messing up the test
> User profiles and security files etc.? Need to get
> Production data files only with out the security files,
> Data area's, etc.
>
> Michael De Gennaro
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: SSegerstrom@xxxxxxxxxxxxxx
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: dsweeney@xxxxxxxxxxxxxxxx
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: miked@xxxxxxxxxxxxxx
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: jmergen@xxxxxxxxxxx
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: miked@xxxxxxxxxxxxxx
>
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: FWSoftware@xxxxxxx
> -- 
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
> Delivered-To: Clare.Holtham@xxxxxxxxxxxxxx
>



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.