CIM Load

[Chris Kelleher]

To any wage slaves still out there:

Environment: NT, 9.0 MFG/Pro, Progress 8.3a, GUI clients

I am trying to do a CIM load in 14.13.1 and am having various problems. At
least this time I remembered to work with a character client, so that is not
one of the problems.

1) Al I want to do is put in a routing code, operation, start date and work
center. I can't seem to come up with the entries that will consistently
work. (see sample below)
2) I am trying to use the @errordatafile entry but no matter what I put for
a file name, I get an error when I do the CIM load. It complains about input
file length being too long. If I don't put a file name, I get an error
related to the imputs getting out of sync.

SAMPLE CIM FILE:

@@batchload rwromt.p
@errordatafile c:\cimerr.out
"W1358 " "300" "01/01/00"

"534"

 

[Chris Kelleher]

If I am reading this correctly, you are trying to CIM using a GUI client..
You should not CIM using a GUI client. In some cases it may work, but not
with any consistency.


+---
| James Blankenship
| MFG/PRO Team Manager
| United Systems, Inc.
+---
| jlb@usiatl.com
| http://www.usiatl.com
| Office: 207-885-9902
| Fax: 207-885-9903
| Mobile: 207-450-8577 Nationwide
+---

 

[Chris Kelleher]

Tom,

While I wasn't around last Thursday, I'm in for a bit today. Let me see if
I can offer some insight.

First off, good thing you're using the character routines to CIM into.
Much better than the others, and I know you know this, but there are some
who might not, so this is a preemptive strike against those problems <g>.

I think (although I reserve the right to be wrong) that you're running into
CIM formatting problems. Here are the steps I'd take (and since I don't
have a working character environment, they're almost completely untested).

1. Remove the @@errorfile line to see if the data loads correctly. I am
going to assume that it will, at this point, but this will either prove or
disprove that this line is the (or a) problem.

2. Remove the spaces from the routing code field. There's no reason to add
them in after the data, and they will only slow up processing.

3. The second field, the routing operation, is a numeric field (at least on
my 9.0 system). Putting the value in quotes tells Progress it's a
character field. Drop the quotes on this and all other numeric fields.

4. Ditto for the effective date field. Leave the quotes at home for this.

5. And before you ask, the same is true for logical fields as well. A
simple yes/no, true/false, or even 0/1 (if I dismember correctly) will
work.

6. Of course, remember that not all numbers are numbers. For example, the
part number field is a character field, not numeric...

7. Given that you're working with a CIM file, I suspect part of your email
got cut off by the PEG email servers. Remember that a field with just a
period in it (".") tells the PEG servers to truncate the email at that
point. It looks like you hadn't finished asking your questions or
providing your data. I don't remember if adding a space after the period
is enough, or if it works better with comments added in (such as /* comment
to fool PEG */).

My shots. If you don't get back to me this week, I'll be in early next
week.

Good luck.

Scott
===============================================================
Scott M. Dulecki /* 1998061901 */ +1 616 975 6322
Product Manager scott_dulecki@qad.com
QAD, Inc. http://www.qad.com
1188 East Paris SE Grand Rapids, MI 49546 USA

Next Michigan Progress Users Group: 19 January 2000

All opinions are my own, and don't necessarily reflect those of
any other living being.
===============================================================

 

[Chris Kelleher]

Logical, date & numeric do not care if there are quotes or not. Quotes only
matter for "-" (tab thru field)and '.'. If a period represents the field
and has no quotes, it represents "END-ERROR". If a period represents the
field and is within quotes, it is treated as a period entered in the data
field.

 

[Chris Kelleher]

Hi

Remember that some MFG/PRO transactions (and this is one of them) prompt for
different fields depending on whether you are adding a new record or
maintaining an existing one. In this case (14.13.1) adding a new record
prompts for a standard operation number before prompting for the work centre
and machine number. If the record already exists with a blank standard
operation number the program does not prompt for this value.

Dave Rollinson

Enigma (formerly SIG Europe) - "Facing the Future"
T +44 (0) 116 238 8113 | F +44 (0) 116 238 8112
D +44 (0) 116 239 1210 | M +44 (0) 7801 743 103 http://www.TheEnigma.co.uk
mailto:dave.rollinson@TheEnigma.co.uk