01 .How do I set up a connection to OSS?
Contact a local network service provider to establish a physical connection to the SAP support network and obtain an official IP address. Then, contact SAP, by phone or in writing, to request an OSS connection. The appropriate form, Remote Connection Data Sheet, can be found in the OSS Windows help file. A detailed answer to this question is covered in the training unit establishing a Remote Connection to SAP.
02. How do I get an OSS user ID?
Contact SAP to request an OSS user ID is required. The appropriate form, OSS User Registration, can be found in the OSS Windows help file.
03. How secure is an OSS connection?
An OSS connection can be made completely secure with a combination of a correctly configured hardware router and the SAProuter program. This is an application level gateway program, and is configured so that only connections to or from predefined IP addresses on predefined port numbers will be accepted.
A fully detailed answer to this question is covered in the training unit "Establishing a Remote Connection to SAP."
04. What happens if my problem gets no response from SAP?
First, make certain that you have actually sent the problem to SAP! It is not uncommon for new OSS users to create a problem note, and then forget to click on the Send to SAP button. Simply creating a note in OSS does not mean that SAP will process the problem. You have to explicitly send us the note.
SAP should only be contacted if, after having searching the notes database, you have not found an appropriate solution. Remember that many problems can often be resolved by simply searching the OSS database. These types of problems do not need to be sent to SAP for resolution. Finally, if you have sent a problem to SAP and have not received a reply, perhaps you logged it with too low a priority.
05. Can I reopen a problem note?
Yes.
Over viewing Remote Services
Online Service System (OSS)
06. What if I get too many notes proposed as solutions?
Try to restrict your search criteria. Always be as specific as possible to avoid this problem. For Instance, searching under the term "Business area" will return over 1500 notes!
07. Do I have to create a note to search for solutions?
No. You can perform a search of the notes database without creating a problem note.
08. Do all problem notes have to be sent to SAP?
No. If you can find an applicable note in the database that resolves the problem, there is no need to send the problem to SAP. Even if you did send the note to SAP, the problem resolver would very likely attach the note already contained in the database as a solution to the problem.
09. How can I see a demonstration of the OSS system?
Either by attending a Technical Core Competence training course, or by arranging a demo with your local subsidiary.
10. Do I have 24-hour-a-day access to OSS?
Yes. OSS is available for users 24-hours a day, seven days a week. Only priority 1 problems will receive an after-hours response. All other problems are handled during normal office hours. Occasionally, OSS will have to be shut down for maintenance or upgrades. This normally only happens during the weekends, and you will always have prior warning.
11. Can you run background processing with a lower priority than online activity?
There is no way to specify a lower priority for background processing than for online processing, nor would this have any effect in a distributed client/server environment. However, online processing is normally that is, the memory provided by the operatinginput-output (I/O) intensive system is not utilized, due to waiting for the I/O. These processes are assigned a higher priority by the operating system than processes that fully utilize their time slice, such as jobs where no rolling occurs. As a result, online processing will have a default higher priority. If you have a distributed system, one possible solution would be to roll all of the background processing to one server, while online activities run on other servers.
12. Can I reserve background work processes for individual applications or users?
No. Reservation is only possible for job Class A.
13. Can I assign priorities (job classes) in the function modules "JOB_OPEN," "JOB_SUBMIT" and "JOB_CLOSE?"
No. If Class A or B jobs must be automatically scheduled, schedule a job of the required class and set it to start periodically.
14. Can I influence the priority of the jobs, regardless of the job class?
In distributed systems with a well-designed distribution on the servers see OSS note 24092.
15. Can I save job logs in the database (analogously to the spool)?
There is no such option in the standard.
16. What happens if the background work process needs to be switched and a job is running in that work process?
The instance kernel waits for the job to finish before the background work process is switched to an alternate type. Jobs are never terminated by the system to make way for an op-mode switch.
17. Can job definitions be transported into other clients or systems?
No. Job definitions contain system specific parameters (for example, target host, user, program, operation mode, and so on). Therefore, it would not make sense to develop a transport tool. For similar reasons, copying a job across clients is not a foreseen task. The following trick, however, is possible: A user, who has job administrator authorizations, logs on to the target client. The user enters transaction SM37, so that all jobs in all clients are displayed and with the Job Copy option copies a job from a source client (only steps, no start time).
18. Does the user receive a message if the job is cancelled?
No.
19. How can I set a periodic job to be deleted after a maximum waiting time? For example a job is to run every 15 minutes after 08:00 hours. Automatic deletion will be applicable for each of these jobs, if the job has to wait more than 20 minutes for execution.
Schedule the job with the following parameters:
Start time 08:00 hours
No start after 08:20 hours
Period 15 minutes
For each job, adjust the earliest and latest start time by 15 minutes.
20. How can I set a periodic job to no longer run as of a certain date?
This option is not provided in the standard system. It can, however, be easily implemented with the function modules "JOB_OPEN," "JOB_SUBMIT,"and "JOB_CLOSE" (see OSS note 4751).
21. Are all system parameters listed in the profiles?
Many parameters do not normally require changes and are therefore defined only in the code. Thus parameters exist that are not listed in the default profile or instance profile.
22. How can system parameters be displayed?
You can display the parameters as follows:
Call up the report RSPFPAR using transaction SE38 to display the parameters for the instance on which you are currently logged on. When you double-click on the corresponding line, the origin of the current value appears.
Use transaction TU02 to display the active parameters.
On the operating system level, you can display the parameters using sappfpar.
23. Where can I find documentation?
Documentation is available on the documentation CD. Using transaction RZ11 (type in the parameter name, click on the Display button and the click on the Documentation button.).
In basic or extended maintenance - transaction RZ10 - using the F1 key.
24. Should the profiles for each instance be defined individually, or is it better to have a common profile of them?
The instance profiles are managed centrally, stored in the directory:
Windows NT: \\<SAPGLOBALHOST>\sapmnt\<SAPSID>\sys\profile
Unix: /usr/sap//<SAPSID>/SYS/profile
Therefore, several instances can access the same profile. In some cases, instance profiles must be individually maintained, because each system needs individual settings of the system parameters. In particular it applies:
If different hardware is used for the instances
If the applications are different (for example, FI on one instance and PP on another)
If different code pages are used (for example, West European, Cyrillic, or Japanese)
For the database server
If several systems have common system parameters settings, use a common profile. This gives you the following advantages:
- Simplified maintenance
- Lower rate of errors
Useful OSS Notes
Note # Description
31395 System parameters: Defined where? Displayed how?
21636 RAM extension: Which changes to profile?
39412 How many work processes to configure?
70639 How are batch jobs scheduled?
36280 Background Work Processes Reserved for Job Class A
31503 FAQ: Background jobs
24092 Distribution of background jobs on application server
16201 Background program, timeout, SAPMSSY6
11728 Background jobs with low priority
06604 Deleting job logs at operating system level
00046 SY098 Time limit exceeded
No comments:
Post a Comment