× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks. I'll try that.

Best Regards,

Mon


-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx [mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of system21-request@xxxxxxxxxxxx
Sent: Tuesday, November 06, 2007 2:00 AM
To: system21@xxxxxxxxxxxx
Subject: SYSTEM21 Digest, Vol 5, Issue 110

Send SYSTEM21 mailing list submissions to
system21@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/system21
or, via email, send a message with subject or body 'help' to
system21-request@xxxxxxxxxxxx

You can reach the person managing the list at
system21-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SYSTEM21 digest..."


Today's Topics:

1. [SYSTEM21] 12/MKS (Mon M. Ferriols)
2. Re: [SYSTEM21] 12/MKS (s21.user@xxxxxxxxx)


----------------------------------------------------------------------

message: 1
date: Mon, 5 Nov 2007 17:55:37 +0800
from: "Mon M. Ferriols" <mon.ferriols@xxxxxxxxxxxxxx>
subject: [SYSTEM21] 12/MKS

So much grief from one option....

Has anyone ever encountered components not updating in INP95 when using this option? Like I have a parent part number which was backflushed only hours apart, and one transaction finished completely with all components having an INP95 transaction and another one with selected components not registering at all. I've eliminated all the obvious causes like BOM effectivities, etc...

TIA!
Mon M. Ferriols
Information Technology Department
Ionics EMS, Inc.



------------------------------

message: 2
date: Mon, 5 Nov 2007 07:18:27 -0800 (PST)
from: s21.user@xxxxxxxxx
subject: Re: [SYSTEM21] 12/MKS

There are times when if the INP60 record is in use at the time the transaction is posted that the IN070 pgm will fall over.

IN070 is the program that writes to the INP95/96 files.

When this happens a joblog and program dump are generated usually for user id QPGMR.

This is the one chink in that armor of the manufacturing transaction processor background job.

So, check to see if you have any program dumps for QPGMR around that time.


Cheers.

----- Original Message ----
From: Mon M. Ferriols <mon.ferriols@xxxxxxxxxxxxxx>
To: "system21@xxxxxxxxxxxx" <system21@xxxxxxxxxxxx>
Sent: Monday, November 5, 2007 4:55:37 AM
Subject: [SYSTEM21] 12/MKS

So much grief from one option....

Has anyone ever encountered components not updating in INP95 when using this option? Like I have a parent part number which was backflushed only hours apart, and one transaction finished completely with all components having an INP95 transaction and another one with selected components not registering at all. I've eliminated all the obvious causes like BOM effectivities, etc...

TIA!
Mon M. Ferriols
Information Technology Department
Ionics EMS, Inc.


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.