on 12-09-2004 1:06 PM
Hi all,
does anyone know what the abap statement RSYN is for?
I haven't found anything about it in help docs.
:bus
Hi :bus,
These 'ABAP' commands RSYN are actually references to hidden SAP kernel commands. These commands reside in a file called RSYN.BIN (most likely located at directory usr/sap/STT/SY).
This file, however, is no longer supported (See SAP note 19466), because as from SAP release 4.6A the required logic is placed elsewhere.
Functions controlled via RSYN are kernel functions like the RFC call redirector or the ABAP code analyzer (and of course many more). SAP prohibits the use of these functions and does NOT provide any information on them.
Hope this answers your question.
Regards,
Rob.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi :bus,
Within the SAPMSSY1 program (actually functions for RFC calls and CPIC calls, thus pretty old) SAP uses screens to modularize functions.
The "RSYN >SCONT SYSC ...." command is used for waiting (on a callback from a remote system).
If you look carefully to the screens of SAPMSSY1, you'll see, that they only contain a PBO module or a PAI module. You can imagine what this means: The "contra" part is located in the remote system.
But since this is very old stuff (today we have better tools available in SAP), i would not dive to deep into this.
Regards (and thanx for the points)
Rob.
Hi,
I am getting dump call_function_format_not_sup which showing sapmssy1 program error. i am attaching the dump. plz check and kindly help me.
ABAP/4 runtime error CALL_FUNCTION_FORMAT_NOT_SUP
Occurred on 07.07.2009 at 15:15:18
-
-
RFC data format not supported.
-
-
What happened?
-
-
An error occurred when executing a Remote Function Call.
The current ABAP/4 program "SAPMSSY1" had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
-
-
What can you do?
-
-
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your
SAP system administrator.
-
-
Error analysis
-
-
A data error occurred when executing a Remote Function Call.
The data format used is not supported by the recipient.
-
-
How to correct the error
-
-
A 'Remote Function Call' passed data in the incorrect format or
length. If both the calling program and the called program are
ABAP/4 function modules, there is an error in the
SAP system.
If one of these programs is a CPI-C program which interprets the
RFC log itself, the error has probably occurred because the program
does not conform to the standards defined by SAP.
-
-
-
System environment
-
-
SAP Release.............. "31H"
Application server....... "PCPPROD1"
Network address.......... "10.106.128.71"
Operating system......... "SunOS"
Release.................. "5.6"
Hardware type............ "sun4u"
Database server.......... "PHYPLW02"
Database type............ "ORACLE"
Database name............ "ALP"
Database owner........... "SAPR3"
Character set............ "en"
SAP kernel............... "31I"
Created on............... "Jul 24 2001 05:20:53"
Created in............... "SunOS 5.5.1 Generic_103640-19 sun4u"
Database version......... "ora OCI_73400"
Patch level.............. "616"
Patch text............... " "
Supported environment....
Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE
8.0...*"
SAP database version..... "31I"
Operating system......... "SunOS 5.5.1, SunOS 5.6, SunOS 5.7, SunOS 5.8"
-
-
User, transaction...
-
-
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY13004"
Screen line......... 2
-
-
Information on where termination occurred
-
-
The termination occurred in the ABAP/4 program "SAPMSSY1" in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1".
The termination occurred in line 67
of the source code of program "SAPMSSY1" (when calling the editor 670).
-
-
Source code extract
-
-
000370 ENDMODULE.
000380
000390 MODULE %_RFCDIA_CALL OUTPUT.
000400 "Do not display screen !
000410 CALL 'DY_INVISIBLE_SCREEN'.
000420 PERFORM REMOTE_FUNCTION_DIACALL.
000430 ENDMODULE.
000440
000450 MODULE %_CPIC_START.
000460 IF SY-XPROG(4) = '%RFC'.
000470 PERFORM REMOTE_FUNCTION_CALL USING RFCTYPE_EXTERNAL_CPIC.
000480 ELSE.
000490 CALL 'APPC_HD' ID 'HEADER' FIELD HEADER ID 'CONVID' FIELD CONVID.
000500 PERFORM CPIC_CALL USING CONVID.
000510 ENDIF.
000520 ENDMODULE.
000530
000540
000550 FORM CPIC_CALL USING CONVID.
000560 COMMUNICATION SEND ID CONVID BUFFER HEADER.
000570 IF SY-SUBRC EQ 0.
000580 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000590 ELSE.
000600 MESSAGE A800.
000610 ENDIF.
000620 ENDFORM.
000630
000640
000650 FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).
000660 DO.
-
-
CALL 'RfcImport' ID 'Type' FIELD TYPE.
000680 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000690 RSYN >SCONT SYSC 00011111 0.
000700 ENDDO.
000710 ENDFORM.
000720
000730 FORM REMOTE_FUNCTION_DIASTART.
000740 DO.
000750 CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.
000760 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000770 "Parking position for next request
000780 RSYN >SCONT SYSC 00011111 10.
000790 "ALternativ : Free mode
000800 "COMMIT WORK.
000810 "SYSTEM-CALL FREE MODE 0.
000820 ENDDO.
000830 ENDFORM.
000840
000850 FORM REMOTE_FUNCTION_DIACALL.
000860 SY-XCODE = '%_@no@'.
-
-
Contents of system fields
-
-
SY field contents..................... SY field contents.....................
-
-
-
-
-
-
-
-
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 0
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
-
-
Chosen variables
-
-
Name.......................... Contents.1........2........3....+....4
-
-
-
-
SY-MSGV1
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
TYPE 3
0000
0003
SY-XPROG
22222222
00000000
SY-XFORM
222222222222222222222222222222
000000000000000000000000000000
-
-
Active calls / events
-
-
No.... Program INCLUDE Line Type.... Name.....................
-
-
-
-
-
-
-
-
-
-
-
-
1 SAPMSSY1 SAPMSSY1 67 FORM REMOTE_FUNCTION_CALL
2 SAPMSSY1 SAPMSSY1 30 MODULE %_RFC_START
-
-
Internal notes
-
-
The termination occurred in the function "ab_rfctinfo" of the SAP
Basis System, specifically in line 1178 of the module " ".
The internal operation just processed is "CALY".
-
-
List of ABAP/4 programs affected
-
-
-
-
Program | Load size | Roll size | Gen. date | / time Changed by |
-
-
SAPMSSY1 | 20480 | 83050 | 21.05.1997 | 16:27 | 21.05.1997 | SAP |
-
-
-
-
List of internal tables
-
-
No dump information available
-
-
Directory of application tables (contents)
-
-
Program name........... Contents.1........2........3....+....
-
-
-
-
-
-
SAPMSSY1 TCPIC
-
-
Directory of data areas (administration information)
-
-
No Program name........... Length Gen.date Gen.time Ofst Type Next
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
0 SAPMSSY1 /%_LISTTABLES 3128 -3 DATA
1 SAPMSSY1 stack area 65536 -2 DATA
2 SAPMSSY1 text pool 4064 -1 DATA
3 SAPMSSY1 global data 1136 0 DATA
4 SAPMSSY1 local data 0 1 STCK
5 SAPMSSY1 constant data 647 2 LITL
6 SAPMSSY1 not assigned 0 3 INVL
7 SAPMSSY1 SYST 2232 4 TABL
8 SAPMSSY1 SY 2232 5 TABL
9 SAPMSSY1 RSJOBINFO 84 6 TABL
10 SAPMSSY1 /%_SCREEN 56 7 DATA
11 SAPMSSY1 /%_SYS%% 480 8 DATA
12 SAPMSSY1 TCPIC 70 9 TABL
-
-
Directory of data areas (contents)
-
-
No Program name........... Contents.1........2........3....+....
-
-
-
-
-
-
-
-
0 SAPMSSY1 /%_LISTTABLES |00000x0C000000000x0C0
1 SAPMSSY1 stack area |000x030000ÿÿÿÿ00000000
2 SAPMSSY1 text pool |ÿÿ000006E000000x01R00000
3 SAPMSSY1 global data | 0 x04
4 SAPMSSY1 local data
-
-
ABAP/4 control blocks CONT
-
-
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl Source Line Source code........
-
-
-
-
-- -- -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
146 CLEA 00 83 SAPMSSY1 60 MESSAGE A800.
147 CLEA 00 84 SAPMSSY1 60
148 CLEA 00 85 SAPMSSY1 60
149 CLEA 00 86 SAPMSSY1 60
150 MESS 00 327 SAPMSSY1 60
151 ENDF 00 SAPMSSY1 62 ENDFORM.
156 PERP 02 SAPMSSY1 65 FORM REMOTE_FUNCTI
157 WHIL 00 2 SAPMSSY1 66 DO.
161 WHIL 00 3 SAPMSSY1 66
165 BRAN 05 Branch to 178 SAPMSSY1 66
166 CALY 00 3 87 72 73 73 SAPMSSY1 67 CALL 'RfcImport' I
>>>>> CALY 02 88 P0 SAPMSSY1 67
174 xper 02 22 23 SAPMSSY1 68 PERFORM (SY-XFORM)
176 SYSC 1F SAPMSSY1 69 RSYN >SCONT SYSC 0
177 BRAX 00 Branch to 161 SAPMSSY1 70 ENDDO.
178 WHIL 00 4 SAPMSSY1 70
182 ENDF 00 SAPMSSY1 71 ENDFORM.
187 WHIL 00 2 SAPMSSY1 74 DO.
-
-
End of runtime analysis
-
-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
you can find this statement in some subroutines (e.g. FORM REMOTE_FUNCTION_CALL) of subroutine pool SAPMSSY1.
regards,
:bus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
yes, it is an abap statement. E.g. the syntax check in abap editor says: "The statement 'RSYN' must be followed by other additions."
Last week I've seen it in a function module (4.6C) but I don't remember the name...
regards
:bus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you sure if it's an ABAP statement?
Where did you see it?
There was a kernel component called RSYN, but it's not used anymore.
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.