| Title: | Please read note 1.0 ELP::OSI_APPL_SUPPORT |
| Notice: | Please read note 1.0 |
| Moderator: | DRAGNS::MILLER COM::S_WATTUM |
| Created: | Mon Aug 30 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 516 |
| Total number of notes: | 2729 |
Hi,
When we used FTAM to copy/replace a file from OpenVMS to a Alcatel System 12
switch, we had the following errors.
$ copy/application=FTAM/replace -
SYD-FREQ-CITY.DAT S12MODEL"user password"::"SYD-FREQ-CITY___HTOA"
%FTAM-E-NOTCOPIED, SYS$SYSDEVICE:[CGI.ROBERT.S12_TESTING.WORK2]SYD-FREQ-CITY.DAT
;1 not copied
%FTAM-E-OPEN, copy: cannot open remote destination file S12MODEL"user password":
:"SYD-FREQ-CITY___HTOA"
%FTAM-E-ERR_UABORT, A user ABORT has been received
%COPY-W-NOTCOPIED, SYS$SYSDEVICE:[CGI.ROBERT.S12_TESTING.WORK2]SYD-FREQ-CITY.DAT
;1 not copied
The file already existed at the Alcatel system;
A directory beforehand shows
Directory S12MODEL::"user password"
SYD-FREQ-CITY___HTOA File ID: None
Size: 3/83 Owner: <Unknown>
Created: 1-JAN-1980 00:00:00.00
Revised: 18-FEB-1997 11:23:21.00 (0)
Expires: <None specified>
Backup: <No backup recorded>
Effective: <None specified>
Recording: <None specified>
File organization: Sequential
File attributes: Allocation: 83, Extend: 0, Global buffer count: 0
No version limit
Record format: Undefined, maximum 28 bytes
Record attributes: None
RMS attributes: None
Journaling enabled: None
File protection: System:, Owner:, Group:, World:
Access Cntrl List: None
Total of 1 file, 3/83 blocks.
and then afterwards;
Directory S12MODEL::"user password"
SYD-FREQ-CITY___HTOA File ID: None
Size: 0/83 Owner: <Unknown>
Created: 1-JAN-1980 00:00:00.00
Revised: 18-FEB-1997 11:23:21.00 (0)
Expires: <None specified>
Backup: <No backup recorded>
Effective: <None specified>
Recording: <None specified>
File organization: Sequential
File attributes: Allocation: 83, Extend: 0, Global buffer count: 0
No version limit
Record format: Undefined, maximum 28 bytes
Record attributes: None
RMS attributes: None
Journaling enabled: None
File protection: System:, Owner:, Group:, World:
Access Cntrl List: None
Total of 1 file, 0/83 blocks.
*** Note that the filesize is now 0.
The attached trace shows that the switch sent f-provider-abort-request
complaining about FTAM protocol error (1007) and that the error-source
is initiating-file-service-user.
Can we confirm that we are not violating the FTAM protocol from the trace?
Thanks and regards.
Michael
14:22:02.85749 OSI trace started Tue Mar 4 14:22:02 1997
14:22:03.85749 --> Session
0dff0120 05061301 00160103 14020082 33013134 023100c1 ff010931 820105a0
03800101 a281fd80 02078081 01318202 3100a459 30100201 01060528 c27b0201
30040602 51013010 02010306 0528c27b 02023004 06025101 30100201 05060528
c27b0203 30040602 51013010 02010706 0528c27b 02043004 06025101 300f0201
09060452 01000130 04060251 01618194 30819102 0109a081 8b608188 80020780
a1070605 28c27b01 01a20706 052bce0f 0107a303 020101be 82006928 82006506
02510102 0101a082 005aa058 811c4445 436e6574 2f4f5349 20465441 4d20636f
70792075 74696c69 74798201 00830203 70840305 35008502 05808601 00a7154e
0528c27b 05034e05 28c27b05 024e0528 c27b0501 56044652 45447108 19065331
324f4153
connect-spdu 0d ff 01
connect/accept-item 05 06
protocol-options = '00000000'B 13 01 00
(not able to received extended concatenated spdus)
version-number = 3 16 01 03
session-user-requirements = '0000000010000010'B 14 02 00
( negotiated release functional unit,
duplex functional unit )
calling-ssap-identifier = 1 33 01 31
called-ssap-identifier = 1 34 02 31
user-data c1 ff 01
14:22:03.85749 --> Presentation
31820105 a0038001 01a281fd 80020780 81013182 023100a4 59301002 01010605
28c27b02 01300406 02510130 10020103 060528c2 7b020230 04060251 01301002
01050605 28c27b02 03300406 02510130 10020107 060528c2 7b020430 04060251
01300f02 01090604 52010001 30040602 51016181 94308191 020109a0 818b6081
88800207 80a10706 0528c27b 0101a207 06052bce 0f0107a3 03020101 be820069
28820065 06025101 020101a0 82005aa0 58811c44 45436e65 742f4f53 49204654
414d2063 6f707920 7574696c 69747982 01008302 03708403 05350085 02058086
0100a715 4e0528c2 7b05034e 0528c27b 05024e05 28c27b05 01560446 52454471
08190653 31324f41 53
CP PPDU SET = 31 82 01
{
[0] IMPLICIT SET = a0 03
{
[0] IMPLICIT mode-selector INTEGER = normal-mode 80 01 01
}
[2] IMPLICIT SEQUENCE = a2 81 fd
{
[0] IMPLICIT protocol-version BIT STRING = '1'B 80 02 07
( version-1 )
[1] IMPLICIT calling-presentation-selector OCTET STRING = 81 01
'31'H
[2] IMPLICIT called-presentation-selector OCTET STRING = 82 02
'3100'H
[4] IMPLICIT presentation-context-definition-list a4 59
SEQUENCE =
{
Context-list SEQUENCE = 30 10
{
presentation-context-identifier INTEGER = 1 02 01 01
abstract-syntax-name OBJECT IDENTIFIER = 06 05 28
{1 0 8571 2 1}
SEQUENCE = 30 04
{
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
Context-list SEQUENCE = 30 10
{
presentation-context-identifier INTEGER = 3 02 01 03
abstract-syntax-name OBJECT IDENTIFIER = 06 05 28
{1 0 8571 2 2}
SEQUENCE = 30 04
{
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
Context-list SEQUENCE = 30 10
{
presentation-context-identifier INTEGER = 5 02 01 05
abstract-syntax-name OBJECT IDENTIFIER = 06 05 28
{1 0 8571 2 3}
SEQUENCE = 30 04
{
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
Context-list SEQUENCE = 30 10
{
presentation-context-identifier INTEGER = 7 02 01 07
abstract-syntax-name OBJECT IDENTIFIER = 06 05 28
{1 0 8571 2 4}
SEQUENCE = 30 04
{
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
Context-list SEQUENCE = 30 0f
{
presentation-context-identifier INTEGER = 9 02 01 09
abstract-syntax-name OBJECT IDENTIFIER = {2 2 1 0 1} 06 04 52
SEQUENCE = 30 04
{
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
}
[APPLICATION 1] IMPLICIT fully-encoded-data SEQUENCE = 61 81 94
{
PDV-list SEQUENCE = 30 81 91
{
presentation-context-identifier INTEGER = 9 02 01 09
single-asn1-type [0] ANY = a0 81 8b
-- Abstract Syntax Name
-- ACSE-PCI
-- Presentation Context Identifier
-- 9
14:22:03.85749 --> ACSE
60818880 020780a1 07060528 c27b0101 a2070605 2bce0f01 07a30302 0101be82
00692882 00650602 51010201 01a08200 5aa05881 1c444543 6e65742f 4f534920
4654414d 20636f70 79207574 696c6974 79820100 83020370 84030535 00850205
80860100 a7154e05 28c27b05 034e0528 c27b0502 4e0528c2 7b050156 04465245
44710819 06533132 4f4153
[APPLICATION 0] IMPLICIT aarq SEQUENCE = 60 81 88
{
[0] IMPLICIT protocol-version BIT STRING = '1'B 80 02 07
( version-1 )
application-context-name [1] a1 07 06
application-context-name OBJECT IDENTIFIER =
{1 0 8571 1 1}
called-ap-title [2] ap-title OBJECT IDENTIFIER = a2 07 06
{1 3 9999 1 7}
called-ae-qualifier [3] ae-qualifier INTEGER = 1 a3 03 02
[30] IMPLICIT user-information SEQUENCE = be 82 00
{
IMPLICIT EXTERNAL SEQUENCE = 28 82 00
{
direct-reference OBJECT IDENTIFIER = {2 1 1} 06 02 51
indirect-reference INTEGER = 1 02 01 01
single-asn1-type [0] ANY = a0 82 00
-- Abstract Syntax Name
-- FTAM-PCI
-- Presentation Context Identifier
-- 1
14:22:03.85749 --> FTAM
a058811c 4445436e 65742f4f 53492046 54414d20 636f7079 20757469 6c697479
82010083 02037084 03053500 85020580 860100a7 154e0528 c27b0503 4e0528c2
7b05024e 0528c27b 05015604 46524544 71081906 5331324f 4153
[0] IMPLICIT f-initialize-request SEQUENCE = a0 58
{
[1] IMPLICIT implementation-information 81 1c
GRAPHIC STRING =
DECnet/OSI FTAM copy utility
[2] IMPLICIT present-context-management 82 01 00
BOOLEAN = false
[3] IMPLICIT service-class BIT STRING = 83 02 03
'01110'B
( management-class,
transfer-class,
transfer-and-management-class )
[4] IMPLICIT functional-units BIT STRING = 84 03 05
'00110101000'B
( read,
write,
limited-file-management,
grouping )
[5] IMPLICIT attribute-groups BIT STRING = 85 02 05
'100'B
( storage )
[6] IMPLICIT ftam-quality-of-service 86 01 00
INTEGER = no-recovery
[7] IMPLICIT contents-type-list SEQUENCE = a7 15
{
[APPLICATION 14] IMPLICIT document-type-name 4e 05 28
OBJECT IDENTIFIER = {1 0 8571 5 3}
(ftam-3)
[APPLICATION 14] IMPLICIT document-type-name 4e 05 28
OBJECT IDENTIFIER = {1 0 8571 5 2}
(ftam-2)
[APPLICATION 14] IMPLICIT document-type-name 4e 05 28
OBJECT IDENTIFIER = {1 0 8571 5 1}
(ftam-1)
}
[APPLICATION 22] IMPLICIT initiator-identity 56 04
GRAPHIC STRING = FRED
filestore-password [APPLICATION 17] 71 08 19
GraphicString GRAPHIC STRING = S12OAS
}
}
}
}
}
}
}
14:22:05.85749 <-- Session
0ebc050c 13010015 04000000 00160102 14020002 34023100 c1a43181 a1a00380
0101a281 99830231 00a52c30 07800100 81025101 30068001 02820101 30078001
00810251 01300780 01008102 51013007 80010081 02510161 65308002 0109a080
61808002 0780a107 060528c2 7b0101a2 03020100 a305a103 020100a4 0706052b
ce0f0107 a5030201 01be2d28 2b020101 a026a124 83020320 84030535 00850205
80860100 a70e4e05 28c27b05 034e0528 c27b0501 8802cd40 00000000 0000
accept-spdu 0e bc
connect/accept-item 05 0c
protocol-options = '00000000'B 13 01 00
(not able to received extended concatenated spdus)
tsdu-maximum-size 15 04
of initiator = 0 00 00
of receiver = 0 00 00
version-number = 2 16 01 02
session-user-requirements = '0000000000000010'B 14 02 00
( duplex functional unit )
called-ssap-identifier = 1 34 02 31
user-data c1 a4
14:22:05.85749 <-- Presentation
3181a1a0 03800101 a2819983 023100a5 2c300780 01008102 51013006 80010282
01013007 80010081 02510130 07800100 81025101 30078001 00810251 01616530
80020109 a0806180 80020780 a1070605 28c27b01 01a20302 0100a305 a1030201
00a40706 052bce0f 0107a503 020101be 2d282b02 0101a026 a1248302 03208403
05350085 02058086 0100a70e 4e0528c2 7b05034e 0528c27b 05018802 cd400000
00000000
cpa-ppdu SET = 31 81 a1
{
[0] IMPLICIT SET = a0 03
{
[0] IMPLICIT mode-selector INTEGER = normal-mode 80 01 01
}
[2] IMPLICIT SEQUENCE = a2 81 99
{
[3] IMPLICIT responding-presentation-selector 83 02
OCTET STRING = '3100'H
[5] IMPLICIT presentation-context-definition-result-list a5 2c
SEQUENCE =
{
SEQUENCE = 30 07
{
[0] IMPLICIT result INTEGER = acceptance 80 01 00
[1] IMPLICIT transfer-syntax-name OBJECT IDENTIFIER = 81 02 51
{2 1 1}
}
SEQUENCE = 30 06
{
[0] IMPLICIT result INTEGER = provider-rejection 80 01 02
[2] IMPLICIT provider-reason INTEGER = 82 01 01
temporary-congestion
}
SEQUENCE = 30 07
{
[0] IMPLICIT result INTEGER = acceptance 80 01 00
[1] IMPLICIT transfer-syntax-name OBJECT IDENTIFIER = 81 02 51
{2 1 1}
}
SEQUENCE = 30 07
{
[0] IMPLICIT result INTEGER = acceptance 80 01 00
[1] IMPLICIT transfer-syntax-name OBJECT IDENTIFIER = 81 02 51
{2 1 1}
}
SEQUENCE = 30 07
{
[0] IMPLICIT result INTEGER = acceptance 80 01 00
[1] IMPLICIT transfer-syntax-name OBJECT IDENTIFIER = 81 02 51
{2 1 1}
}
}
[APPLICATION 1] IMPLICIT fully-encoded-data SEQUENCE = 61 65
{
PDV-list SEQUENCE = 30 80
{
presentation-context-identifier INTEGER = 9 02 01 09
single-asn1-type [0] ANY = a0 80
-- Abstract Syntax Name
-- ACSE-PCI
-- Presentation Context Identifier
-- 9
14:22:05.85749 <-- ACSE
61808002 0780a107 060528c2 7b0101a2 03020100 a305a103 020100a4 0706052b
ce0f0107 a5030201 01be2d28 2b020101 a026a124 83020320 84030535 00850205
80860100 a70e4e05 28c27b05 034e0528 c27b0501 8802cd40 00000000 0000
[APPLICATION 1] IMPLICIT aare SEQUENCE = 61 80
{
[0] IMPLICIT protocol-version BIT STRING = '1'B 80 02 07
( version-1 )
application-context-name [1] a1 07 06
application-context-name OBJECT IDENTIFIER =
{1 0 8571 1 1}
result [2] associate-result INTEGER = accepted a2 03 02
result-source-diagnostic [3] acse-service-user [1] a3 05 a1
INTEGER INTEGER = Message number 00000000
responding-ap-title [4] ap-title OBJECT a4 07 06
IDENTIFIER = {1 3 9999 1 7}
responding-ae-qualifier [5] ae-qualifier INTEGER = 1 a5 03 02
[30] IMPLICIT user-information SEQUENCE = be 2d
{
IMPLICIT EXTERNAL SEQUENCE = 28 2b
{
indirect-reference INTEGER = 1 02 01 01
single-asn1-type [0] ANY = a0 26
-- Abstract Syntax Name
-- FTAM-PCI
-- Presentation Context Identifier
-- 1
14:22:05.85749 <-- FTAM
a1248302 03208403 05350085 02058086 0100a70e 4e0528c2 7b05034e 0528c27b
05018802 cd400000 00000000
[1] IMPLICIT f-initialize-response SEQUENCE = a1 24
{
[3] IMPLICIT service-class BIT STRING = 83 02 03
'00100'B
( transfer-class )
[4] IMPLICIT functional-units BIT STRING = 84 03 05
'00110101000'B
( read,
write,
limited-file-management,
grouping )
[5] IMPLICIT attribute-groups BIT STRING = 85 02 05
'100'B
( storage )
[6] IMPLICIT ftam-quality-of-service 86 01 00
INTEGER = no-recovery
[7] IMPLICIT contents-type-list SEQUENCE = a7 0e
{
[APPLICATION 14] IMPLICIT document-type-name 4e 05 28
OBJECT IDENTIFIER = {1 0 8571 5 3}
(ftam-3)
[APPLICATION 14] IMPLICIT document-type-name 4e 05 28
OBJECT IDENTIFIER = {1 0 8571 5 1}
(ftam-1)
}
[8] IMPLICIT checkpoint-window INTEGER = 52544 88 02 cd
}
}
}
}
}
}
}
14:22:05.85749 --> Session
01000100 6182006f 3082006b 02010181 820064b6 03800102 aa3b8001 036c32a0
16191453 59442d46 5245512d 43495459 5f5f5f48 544f4181 0305bf80 a213a011
4e0528c2 7b0503a0 08300681 011c8201 01430200 30b21e80 020330a1 15a113a0
114e0528 c27b0503 a0083006 81011c82 01018301 00b800
give-tokens-spdu 01 00
data-spdu 01 00
14:22:05.85749 --> Presentation
6182006f 3082006b 02010181 820064b6 03800102 aa3b8001 036c32a0 16191453
59442d46 5245512d 43495459 5f5f5f48 544f4181 0305bf80 a213a011 4e0528c2
7b0503a0 08300681 011c8201 01430200 30b21e80 020330a1 15a113a0 114e0528
c27b0503 a0083006 81011c82 01018301 00b800
[APPLICATION 1] IMPLICIT fully-encoded-data SEQUENCE = 61 82 00
{
PDV-list SEQUENCE = 30 82 00
{
presentation-context-identifier INTEGER = 1 02 01 01
[1] IMPLICIT octet-aligned OCTET STRING = 81 82 00
-- Abstract Syntax Name
-- FTAM-PCI
-- Presentation Context Identifier
-- 1
14:22:05.85749 --> FTAM
b6038001 02aa3b80 01036c32 a0161914 5359442d 46524551 2d434954 595f5f5f
48544f41 810305bf 80a213a0 114e0528 c27b0503 a0083006 81011c82 01014302
0030b21e 80020330 a115a113 a0114e05 28c27b05 03a00830 0681011c 82010183
0100b800
[22] IMPLICIT f-begin-group-request SEQUENCE = b6 03
{
[0] IMPLICIT threshold INTEGER = 2 80 01 02
}
14:22:05.85749 --> FTAM
aa3b8001 036c32a0 16191453 59442d46 5245512d 43495459 5f5f5f48 544f4181
0305bf80 a213a011 4e0528c2 7b0503a0 08300681 011c8201 01430200 30b21e80
020330a1 15a113a0 114e0528 c27b0503 a0083006 81011c82 01018301 00b800
[10] IMPLICIT f-create-request SEQUENCE = aa 3b
{
[0] IMPLICIT override INTEGER = 80 01 03
delete-and-create-with-new-attributes
[APPLICATION 12] IMPLICIT initial-attributes SEQUENCE = 6c 32
{
[0] IMPLICIT filename SEQUENCE = a0 16
{
filename-attribute GRAPHIC STRING = 19 14
SYD-FREQ-CITY___HTOA
}
[1] IMPLICIT permitted-actions BIT STRING = 81 03 05
'10111111100'B
( read,
replace,
extend,
erase,
read-attributes,
change-attributes,
delete-file,
traversal )
contents-type [2] document-type [0] IMPLICIT a2 13 a0
SEQUENCE =
{
[APPLICATION 14] IMPLICIT document-type-name OBJECT 4e 05 28
IDENTIFIER = {1 0 8571 5 3} (ftam-3)
parameter [0] parameters SEQUENCE = a0 08 30
{
[1] IMPLICIT maximum-string-length INTEGER = 28 81 01 1c
[2] IMPLICIT string-significance INTEGER = fixed 82 01 01
}
}
}
[APPLICATION 3] IMPLICIT requested-access BIT STRING = 43 02 00
'00110000'B
( replace,
extend )
}
14:22:05.85749 --> FTAM
b21e8002 0330a115 a113a011 4e0528c2 7b0503a0 08300681 011c8201 01830100
b800
[18] IMPLICIT f-open-request SEQUENCE = b2 1e
{
[0] IMPLICIT processing-mode BIT STRING = '00110'B 80 02 03
( replace,
extend )
contents-type [1] proposed [1] document-type [0] a1 15 a1
IMPLICIT SEQUENCE =
{
[APPLICATION 14] IMPLICIT document-type-name OBJECT 4e 05 28
IDENTIFIER = {1 0 8571 5 3} (ftam-3)
parameter [0] parameters SEQUENCE = a0 08 30
{
[1] IMPLICIT maximum-string-length INTEGER = 28 81 01 1c
[2] IMPLICIT string-significance INTEGER = fixed 82 01 01
}
}
[3] IMPLICIT recovery-mode INTEGER = none 83 01 00
}
14:22:05.85749 --> FTAM
b800
[24] IMPLICIT f-end-group-request SEQUENCE = b8 00
{
}
}
}
14:22:08.85749 <-- Session
07031801 04
prepare-spdu 07 03
prepare-type = %x04 18 01 04
14:22:08.85749 <-- Session
196a1101 03c165a0 63a02e30 07020101 06025101 30080202 00830602 51013007
02010506 02510130 07020107 06025101 30070201 09060251 01613130 80020109
a0806480 800100be 1d281b02 0101a016 a5144501 026d0f30 0d800102 810203ef
82010483 01010000 00000000
abort-spdu 19 6a
transport-disconnect = '00000011'B 11 01 03
(
transport connection is released
alignment fault reporting already enabled
user abort)
user-data c1 65
14:22:08.85749 <-- Presentation
a063a02e 30070201 01060251 01300802 02008306 02510130 07020105 06025101
30070201 07060251 01300702 01090602 51016131 30800201 09a08064 80800100
be1d281b 020101a0 16a51445 01026d0f 300d8001 02810203 ef820104 83010100
00000000 00
[0] IMPLICIT aru-ppdu SEQUENCE = a0 63
{
[0] IMPLICIT presentation-context-indentifier-list a0 2e
SEQUENCE =
{
SEQUENCE = 30 07
{
presentation-context-identifier INTEGER = 1 02 01 01
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
SEQUENCE = 30 08
{
presentation-context-identifier INTEGER = 131 02 02 00
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
SEQUENCE = 30 07
{
presentation-context-identifier INTEGER = 5 02 01 05
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
SEQUENCE = 30 07
{
presentation-context-identifier INTEGER = 7 02 01 07
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
SEQUENCE = 30 07
{
presentation-context-identifier INTEGER = 9 02 01 09
transfer-syntax-name OBJECT IDENTIFIER = {2 1 1} 06 02 51
}
}
[APPLICATION 1] IMPLICIT fully-encoded-data SEQUENCE = 61 31
{
PDV-list SEQUENCE = 30 80
{
presentation-context-identifier INTEGER = 9 02 01 09
single-asn1-type [0] ANY = a0 80
-- Abstract Syntax Name
-- ACSE-PCI
-- Presentation Context Identifier
-- 9
14:22:08.85749 <-- ACSE
64808001 00be1d28 1b020101 a016a514 4501026d 0f300d80 01028102 03ef8201
04830101 00000000 0000
[APPLICATION 4] IMPLICIT abrt SEQUENCE = 64 80
{
[0] IMPLICIT abort-source INTEGER = acse-service-user 80 01 00
[30] IMPLICIT user-information SEQUENCE = be 1d
{
IMPLICIT EXTERNAL SEQUENCE = 28 1b
{
indirect-reference INTEGER = 1 02 01 01
single-asn1-type [0] ANY = a0 16
-- Abstract Syntax Name
-- FTAM-PCI
-- Presentation Context Identifier
-- 1
14:22:08.85749 <-- FTAM
a5144501 026d0f30 0d800102 810203ef 82010483 01010000 00000000
[5] IMPLICIT f-provider-abort-request SEQUENCE = a5 14
{
[APPLICATION 5] IMPLICIT action-result 45 01 02
INTEGER = permanent-error
[APPLICATION 13] IMPLICIT diagnostic SEQUENCE = 6d 0f
{
diagnostic SEQUENCE = 30 0d
{
[0] IMPLICIT diagnostic-type INTEGER = 80 01 02
permanent
[1] IMPLICIT error-identifier INTEGER = 1007 81 02 03
[2] IMPLICIT error-observer INTEGER = 82 01 04
responding-file-protocol-machine
[3] IMPLICIT error-source INTEGER = 83 01 01
initiating-file-service-user
}
}
}
}
}
}
}
}
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 505.1 | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Wed Mar 05 1997 08:07 | 14 | |
You're going to need to ask Alcatel what they think is wrong. They are sending back a 1007 error - which translates to "protocol error, unspecific" - not really very helpful. There doesn't seem to be anything wrong in the request we are sending. I seem to recall, some time ago, possible problems with Alcatel and COPY/REPLACE. My memory may be incorrect, but they may not know how to correctly handle an f-create-req with an override of 'delete-and-create-with-new-attributes' What happens if the file exists and you try the COPY without the /REPLACE? Tried the /OVERLAY option? --Scott | |||||
| 505.2 | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Wed Mar 05 1997 08:37 | 7 | |
My memory must be failing. A quick search does not turn up anything specific to Alcatel. However, IBM did apparently have some problems in this area. If IBM and Alcatel are using a common ancestor (like the RETIX FTAM or ISODE) then you might be expected to see similar problems (note 382 I think). In any event, you'll still need to involve Alcatel to see what they think is wrong. --Scott | |||||
| 505.3 | GIDDAY::YU | Thu Mar 06 1997 00:26 | 27 | ||
Hello Scott, Thanks for the replies. You are correct in saying that Alcatel did not know how to handle f-create-req with delete-and-create-with-new-attributes. We had that experience last year on a unix system. The error they sent back was 3023 "Override not possible". The problem was reported to Alcatel by our customer. This time the same problem happened on an OpenVMS system when communicating with the Alcatel System 12. Alcatel provided a patch which was supposed to solve this "Override not possible" problem. After the patch was applied, they sent the 1007 "FTAM protocol error (unspecific)" error. I agree with you that there seems to be nothing wrong in the f-create-req we sent. We just want to make sure before we ask the customer to further pursue the problem with Alcatel. >What happens if the file exists and you try the COPY without the /REPLACE? >Tried the /OVERLAY option? We'll ask the customer to try and see what happens. Thanks and regards. Michael | |||||
| 505.4 | GIDDAY::YU | Fri Mar 07 1997 01:32 | 16 | ||
Hello Scott,
When the file exists in the Alcatel system and we use copy/overlay, the
error-identifier returned is 3012 (file busy).
When the file exists in the Alcatel system and we use copy without
qualifier, the error-identifier returned is 3005 (file already exists).
When the file does not exist in the Alcatel system and we use copy
without qualifier, the error-identifier returned is 3000 (file not
found).
Regards.
Michael
| |||||
| 505.5 | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Fri Mar 07 1997 07:56 | 1 | |
sounds like they are seriously broken. | |||||
| 505.6 | OSIF_OVR_DEL_CRE_OLD_ATTRIB in copy command?? | GIDDAY::YU | Mon Mar 10 1997 18:59 | 20 | |
Hello Scott,
We had a discussion with the FTAM technical support in Alcatel. They
claimed that they did not support override. However they put in some
coding to allow some kind of override actions. The only override action
they support (with the new coding) is f-create-request with
delete-and-create-with-old-attributes (OSIF_OVR_DEL_CRE_OLD_ATTRIB in
our case).
We understand that we can do this using FTAM programming. Can we do the
same using copy commands? We have been through the various qualifiers
and it seems that we cannot use the copy command to generate a
f-create-request with delete-and-create-with-old-attributes. Are we
correct to say that we can do that only by FTAM programming?
Thanks and regards.
Michael
| |||||
| 505.7 | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Mon Mar 10 1997 23:45 | 12 | |
How can they not support override? How do they expect to be able to interoperate with anyone? Well, unfortunately, you are correct in that there is no way to get us to generate delete_and_create_with_old except via the API. I don't suppose you'd be interested in being a field test site for FTAMlite? Not that it will help you in the utilities area, but it's looking to be a better API. --Scott | |||||
| 505.8 | GIDDAY::YU | Tue Mar 11 1997 18:46 | 25 | ||
Hello Scott,
Thanks for the prompt reply. We'll inform our customer that they have
to go for the API.
During our discussion with Alcatel, we were told that the reason of not
supporting override is because of the file system on the switches.
Every file needs to be pre-created!!
I agree that they have not implemented the 'full' FTAM. They only
provide a way for people to retrieve billing data from their switches
using FTAM.
We have not heard about FTAMlite. What is it about? Is it some
implementation of FTAM which provides better utilities and better API?
I'll be interested to know more about FTAMlite, but I don't think we
are qualified to be a field test site because we only have OpenVMS and
unix (alpha) machines that run FTAM. We do not have any third-party
implementation for testing.
Thanks and regards.
Michael
| |||||
| 505.9 | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Tue Mar 11 1997 20:11 | 25 | |
FTAMlite is my midnight project which we are currently looking at releasing in the next release of DECnet-Plus. While EDS wouldn't normally do this, a large portion of the code work was done prior to the transition, and FTAMlite will have a number of other advantages for EDS. The goal is to eventually phase out the existing API code in preference for FTAMlite. Anyway, FTAMlite is a ground-up rewrite of FTAM, providing a backwards compatible FTAM API. The re-write was done in C++, with an idea toward eventually providing a class library interface (however, this phase of the project is still being discussed). The new code is better mainly in terms of performance, and hopefully stability, (it's smaller and doesn't leak memory amoung other things) but provides the same capabilities as the current API (with the exception of FERPM support, planned for a later phase - the one in discussion). Actually, it has more capabilities in it, but the backward compatible API places constraints on what is allowed - additional document types, for example, cannot be implemented with the old API even though FTAMlite supports them. Since you're interoperating with Alcatel, and looking at the existing FTAM API, the customer may want to consider being an FT site. FTAMlite is currently only available on OpenVMS Alpha though. FT kits for other platforms are still a few months out. --Scott | |||||