| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3040.1 | | SYSTEM::newdial_4.reo.dec.com::JOHNSON | Richard Johnson , http://samedi.reo.dec.com | Wed Mar 05 1997 16:16 | 6 |
| Pettri
Could you paste here the TUN_SUPU element definition?
Thanks
Richard
|
| 3040.2 | EDI Definfitions sucked into the map | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Wed Mar 05 1997 17:30 | 7 |
| Pertti,
I notice the definition source is 'local' i.e. its been changed. Have
you confirmed that Filebridge has the latest version of the EDI
document definition in its map?
Graham
|
| 3040.3 | | IJSAPL::DEWIJK | GJ from the Dutchlands | Wed Mar 05 1997 21:29 | 8 |
| and,
after the changing of the definitions, is the cache rebuilt and
replaced?
You talk about the internal file, what does the external file look
like? also three positions?
GJ
|
| 3040.4 | Routing within one node! | EEMELI::PLAHTEENMAKI | | Fri Mar 07 1997 11:29 | 87 |
| Hi and thanks for your interest!
DEC/EDI is a version 1.3
JOPOX:: Application services DECNET 1.3
VAX/VMS V6.1 on node JOPOX 7-MAR-1997 10:29:35.21 Uptime 10 17:23:41
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
The situation here is that I use filebrige to put files in a DEC/EDI- client and
a customer has a program that fetches file directly from client, so there isn't
any translation made. It's kind of client to client routing, which is possible
in DEC/EDI v1.3. This is done like this because the customer wants so and they
have an API already done between DEC/EDI and MUMPS-application.
This is from filebridge
SEGMENT TUN; /* Tunnistetiedot */
01 ELEMENT_PONI ; /* M*/
02 TUN_PONI CH SIZE 50; /* O POTILASNIMI*/
01 ELEMENT_HETU ; /* M*/
02 TUN_HETU AN SIZE 11; /* O HENKILOTUNNUS*/
01 ELEMENT_SUPU ; /* M*/
02 TUN_SUPU N SIZE 01; /* O SUKUPUOLI*/
******************************************************************************
This are definitions from DEC/EDI
Standard : EDIF 1
Element ID : SUPU Definition Source : Local
Position Dictionary No. Requirement
0001 SUPU O
Standard : EDIF 1 Partner ID :
Document Type External Document Description Definition
Document Source
PYVAYL PYVAYL PYYNTO_VASTAUS_YLEINEN Local
Group Type : Controlling Agency : Version : 1 Release :
Segment Position Segment ID Requirement Definition Source
0002 TUN M Local
Description Area Loop ID Loop Count Repeat
Tunnistetiedot D 0 1
Loop Requirement
Element Position Element ID Requirement Definition Source
0003 SUPU M Local
Element ID : SUPU
Sub-Element Position Dictionary Number Definition Source Requirement
0001 SUPU Local O
Description : SUKUPUOLI
Min Length : 1
Max Length : 1
Data Type : N
Justification : R
Pad Character :
Data Label : TUN_SUPU
Default :
Standard : EDIF 1
Definition Source : Local
Segment ID Segment Description
TUN Tunnistetiedot
Position Element ID Requirement
0001 PONI M
0002 HETU M
0003 SUPU M
0004 TILA O
0005 LAHE M
0006 SAKU O
0007 TUNU O
Thanks!
Pertti
|
| 3040.5 | more | EEMELI::PLAHTEENMAKI | | Fri Mar 07 1997 12:14 | 27 |
| Here I include alse filebridge degub.log
FB SEGMENT: TUN;
DEFAULT SOURCE INSTANCE: RIVI_S{1}
TUN_PONI = if(RIVI_REC.NIMI <> ' ') then RIVI_REC.NIMI;
VALUE SET TO: "TERVE TEEMU "
TUN_HETU = if(RIVI_REC.HENKILOTUNNUS <> ' ') then
$SUBSTR(1,6,RIVI_REC.HENKILOTUNNUS)|'-'|$SUBSTR(7,4,RIVI_REC.HENKILOTUNNUS);
VALUE SET TO: "121212-TETM"
TUN_SUPU = if(RIVI_REC.SUKUPUOLITUNNUS <> ' ') then
$INT(RIVI_REC.SUKUPUOLITUNNUS);
VALUE SET TO: "1"
TUN_LAHE = if(RIVI_REC.NIMI <> ' ') then '1' ;
VALUE SET TO: "1"
Last Modified Date : 03-MAR-1997 10:32
Still in dump you can see, its 3 char log.
Record number 51 (00000033), 14 (000E) bytes, RFA(0003,0000,00C0)
2020 31203A20 55505553 5F4E5554 TUN_SUPU : 1 .. 000000
|