SCSM 2012 - Setting Cube Job Schedule

I would like to set the Process.SystemCenterConfigItemCube to run every 24 hours at 02:00. I have something wrong in the criteria below, what is it? I am fairly sure its to do with the DailyFrequency.
Set-SCDWJobSchedule -JobName Process.SystemCenterConfigItemCube -ComputerName GBPRDSCSM02
-DailyFrequency 24:00 -DailyStart 02:00

Hmm. It seems the set-scdwjobschedule cmdlet is a little weird:
This works:
Set-SCDWJobSchedule -JobName Process.SystemCenterConfigItemCube -ScheduleType Daily -DailyStart 06:00 -DailyFrequency 23:59
This doesn't work -> throwing an error because of the -DailyFrequency 24:00:
Set-SCDWJobSchedule -JobName Process.SystemCenterConfigItemCube -ScheduleType Daily -DailyStart 06:00 -DailyFrequency 24:00
Only option I can see is run the cmdlet with -DailyFrequency 23:59 and modify the frequency afterwards in the SCSM console - Data Warehouse -> Data Warehouse Jobs
Andreas Baumgarten | H&D International Group

Similar Messages

SCSM 2012 Change form issue - Scheduled start and end times default to 12:00:00

I have a report that the Change Form in SCSM 2012 is not allowing users to set the scheduled start and end times. The date stays correct, but the time reverts back to 12:00:00, and the user has to save to the initial form, then re-open and
change the times.
I checked in the authoring tool, the time/date field is set to full date and time. (I think these are custom fields)
I am not sure where else to look to adjust any settings as needed.
Thanks for any assistance.
Joshua Fuente

Hi Joshua,
Is this situation on all consoles or few ones? Check the time format on the user's PC. 24h or 12h could affect the DateTime control's behavior.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Facebook:

About Job schedule

Hi,
I use pl/sql developer---> jobs to set my job schedule.
Today,my job isn't work and error message ORA-12011 and ORA-06512.
I don't know how to edit it.
jing

This is my code:
begin
sys.dbms_job.submit(job => :job,
                      what => '
submitter.package.method;',
                      next_date => to_date('30-11-2005', 'dd-mm-yyyy'),
                      interval => 'TRUNC(SYSDATE+1)');
commit;
end;
submitter.package.method these tree parameters I have filled the correct values.
Yesterday, I clicked 'run' and it could execute but today it doesn't work.This job must run once everyday.

Window Server 2012 R2 Job Scheduler Failing.

Hi,
Currently, my company's Window Server 2012 R2 job scheduler having a problem.
Then i found out the solution at http://support.microsoft.com/kb/2617046, so i download the hotfix to fix the problem. However, i get another error as below.
Please, what can i do?
Thanks
Best Regard
Vincent.

Amy,
Thanks for the tips, I follow the settings. I checked the condition and troubleshoot according to the lists you provided.
The task was configured to run only when a specified network is available. (Not set this)
The configured expiration time for the task has passed. (no expired time set)
The task is configured to ignore or queue a new task instance if a previous instance is still running. (not set this)
The task is configured not to run when the computer is on battery power. (yes, will not run when computer on battery power. will not happen because is a server all the time running AC power).
The task is configured to run only if a specific user is logged on. (must select this, if not, the scheduler will not run at all)
The task was disabled by a user. (is enabled)
The previous task instance might have been running longer than expected because a component is busy processing data. If the task is normally expected to run for this length of time, consider modifying the task triggers to take this run-time length
into consideration, or configure the task to be terminated after a preset time. (already set "Stop the task if runs longer than 3 days" and "If the running task does not end when requested, force it to stop". and "Do not start
a new instance " had been set)
Frankly, for the moment it run normally, somehow, I don't know when the incident will happen again. It seem randomly happen, and not by default. That is why kinda need the fix to fix this bug. Cannot trigger email when this incident happen.
And the schedule we run is highly critical.
Thanks.

SQL Server Agent Job Scheduler- Set time less than 10 seconds

Hi,
Could any one please let me know how to change the SQL server agent Job scheduler time to less than 10 secs?
I wan to schedule a SSIS package run for every 5 secs.
Thanks..

Be careful, it is a bad idea to blindly just issue a new package run without knowing whether the previous package ended.
It may lead to locking/dead-locking.
Now re the Agent: the seconds are not exposed at all, why you say 10?
But, there is a way, not through the UI, explained there:http://stackoverflow.com/questions/5569415/is-there-a-way-to-set-a-sql-server-job-scheduled-to-run-every-30-seconds + http://www.sqlservercentral.com/articles/Administration/sqlserverjobscheduling/2288/
PS you can have it every sec
Arthur My Blog

Error while creating SCSM 2012 sp1 self-portal on SP2013

Hell to everyone
today dive into SCSM installation and self-service portal setup. the environment i use is as following:
Windows 2008 R2 Datacenter x64 SP1
SQL 2012 BI Edition
Sharepoint server 2013 Enterprise Edition
SCSM 2012 SP1
i have successfuly set up SCSM 2012. everything is workig fine.
but when i go to sel-service portal setup (all components on one server - both Web-Content server and SP WebParts) i face with an error
_CreateSharePointWebSite.F175D191_81C3_4A7D_A05B_6A250575B468
the error is related to Site creation and SP webparts installation.
i tried to setup just Web-Content Server and installation was finished successfully.
Please help me with the issue! very urgently
there is no honda without racing

Hi Pavel,
According to your description, my understanding is that you got an error when you set up Service Manager 2012 SP1 running on SharePoint 2013.
Please check whether you have configured SCSM and SharePoint 2013 correctly. You can check as the following link:
http://blogs.technet.com/b/thomase/archive/2013/08/19/how-to-get-service-manager-2012-self-service-portal-running-on-sharepoint-2013.aspx
Please make sure you used the same account to instal SharePoint and Service manager.
If this issue still exists, please do as the followings:
Open Central Administration\Monitoring\Review job defintions, select the servers in the farm one-by-one , then click Application Server Administration Service Timer Job, click Disable.
Restart "Sharepoint 2010 Timer " in services.msc on all servers in the farm.
Try to install the SCSM portal.
Click Central Administration\Monitoring\Review job defintions\Application Server Administration Service Timer Job, click Enable.
Restart "Sharepoint 2010 Timer " in services.msc on all servers in the farm
Here are some similar links for your reference:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/47d43d25-6e14-464a-b899-c13dcbad880f/error-while-installing-service-manager-selfservice-portal?forum=sharepointcustomizationprevious
http://scug.be/valerie/2011/12/01/scsm-2012-self-service-portal-setup-can-t-create-a-new-site/
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

SCSM 2012 - Business services reporting

When reporting on business services I go to the ConfigItem Cube
When I look at the ServiceDim there is an option for 'Business Detailed Descripion'. This is always blank when I report on it.
When I set up business services in SCSM 2012 I do not see a field called 'Business Detailed Descripion' - where should i enter this information in SCSM 2012 so that I can add it to my report?
tamrep

Hi Tamrep,
If you open Business service in the Authoring Tool and you explore in the class properties, you will see the "Business Detailed Description" field.
But this is not by default available in your form. If you want, you can add this field with the Authoring tool to the business service form and make it available.
Regards,
Dennis

SCSM 2012 - Problems running script in custom workflow

Hi all,
I'm trying to create a custom workflow in the Authoring Tool that will send an email when a ticket in certain queues is unassigned, but I only want this to run during business hours. I've created the PowerShell script, and it runs great on its own.
However, whenever I try to add any kind of scripting event to a custom workflow, the workflow fails:
Microsoft.EnterpriseManagement.Common.InconsistentDataException: The requested objects had an unknown management pack. ---> Microsoft.EnterpriseManagement.Common.InconsistentDataException: The call produced inconsistent results. The data on the client
does not match the data returned from the server. The most likely cause is that client-side cache is out of sync with server data. ---> Microsoft.EnterpriseManagement.Common.ObjectNotFoundException: An object of class ManagementPack with ID %GUID% was not
found...
If I create and import a management pack with an empty workflow, the workflow succeeds. If I use the "Add AD DS User to Group", the workflow succeeds. But as soon as I add a scripting event, the workflow fails.
For testing, I added a PowerShell event with this code:
$a=1
I also added a Command Script event with this code and got the same error as above: ping SomeServer
I even tried a VBScript, but that caused the workflow to not run at all:
dim someVariable
someVariable = "some value"
I then disabled the VBScript activity and the workflow runs successfully.
I'm running SCSM 2012 SP1 with UR4. I am copying the .dll file into the SCSM installation directory (which is not in the default location). The GUID referenced in the error code is the GUID for my custom MP.
This is my first time creating a custom workflow in the Authoring Tool. Can you tell me what I'm missing? Please let me know if you need any more information
Thanks!
Marnie

Thanks, Anders. I had seen that issue in my searches on this problem. I had tried both the manual fix suggested in that post as well as upgrading to UR4 (so I'm on on SP1 UR4). Neither approach made any difference.
Am I supposed to do anything with the .cs, .xoml, and .xomlx files that also get generated? I noticed that if I move ALL the associated files into the install directory (not just the .dll file), then import the MP, I get a different error. Instead of the
MP being missing, the error is now:
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.ServiceManager.WorkflowAuthoring.ActivityLibrary.WindowsPowerShellScript.Activity_Closed(Object sender, ActivityExecutionStatusChangedEventArgs e)
   at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()
This makes it seem like I do need to move ALL the files to the install directory, but maybe now the workflow just doesn't like my code?
Thanks!
Marnie

SCSM 2012 queries

hi
i have recently upgraded SCSM 2012 from 2010. Just few queries to be clarified...
1. Users are able to access the create request page only when i add the domain\users group in Groups -> Incident catelog -> global operators group. Is this right?
2. On the File attachment part while creating incident, i have done as per the link found in google as under published reqeust offering page and added the additional user prompt for file attachment and saved it. Now only domain admins and administrators
can access this file attachment page. It is not coming for normal users. Is there any specific permission to be given?
3. On the anouncements part, can i able to increase or decrease the fonts?
4. I need an approval process for incidents.. how to make sure certain incident categories are approved through portal?
regards Sundaresan.C

have you considered applying the latest rollup? There is a critical performance fix in UR2, which does not sound like what you are describing, but on the off chance that you are explaining things differently.
Also consider adding a second management server and connect to this. A long shot, but could rule out an "behind the curtains" performance issue.
Another long shot is to move the SM DB to its own SQL box. Also I am getting alot of Page Life expectancy is low alarms in SCOM, and we suspect some backup jobs to be the culprit. Not that it would explain issues in day-to-day operations.
Service Manager also has a tracing tool (not sure it is documented anywhere than MS internal support channels). you may be able to read something out of it. Post stuff here and we will try an decipher it.
Please use the following procedure to get Service Manager Traces and try to reproduce the same operations
on both consoles.
StartTrace:
         Open a command prompt
         Switch to the SCSM install folder\Tools
directory
         tracelogsm.exe -start Perftrace -guid
Performance.ctl -f c:\Perftrace.etl -rt -flag 0x300FF010 -level 5 -ft 2 -cir 100
Reproduce the behavior
Stop trace:
         tracelogsm.exe -stop Perftrace
Format Trace:
         set TRACE_FORMAT_PREFIX=[%9!d!]%8!04X!.%3!04X!::%4!s![%!FLAGS!][%!LEVEL!][%!FUNC!]
         TraceFmtSM.exe -f C:\performance.etl
-tmf SvcMgrTrace.tmf -o PerfTrace.txt
http://codebeaver.blogspot.dk/

Reporting Tab is not showing in SCSM 2012 SP1 Console

I'm working with SCSM 2012 SP1. But after installing data ware house only "DataWareHouse" tab appares no "Reporting" tab. And it shows below MSG:
And only the below reporting management pack are available in the Data Ware House >> Management pack area.
I already check data warehouse server 'System Center Data Access Service' and 'SQL Server reporting Service', borth are running. But still 'Reporting' tab is not there.
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

At last I solve the problem. THere is 2 solution for resolve the issue.
Force start all warehouse job.
Un register and reregistared DataWareHouse againg.
In my case I do the borth after reregister datawarehouse I wait 1hr after that I manualy start the warehouse jobs. And it works for me.
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Periodic background job scheduling

Hello fellow SDNers,
I have a background job which has to run periodically. So I schedule it in SM36 to run after every 10 minutes and it executes without a problem. However, I have a scenario which requires that the next execution of the job should happen only after ensuring that the first one is not active (either it should have finished execution or aborted with error).
I need to understand the options available to handle this. Of course there is an option of writing another program to handle these jobs dynamically using JOB_OPEN, JOB_SUBMIT etc. or to create an event and trigerring it through another program and setting the job to run after this.
Is there any other option/setting available which can save me from the programming effort (which i wish to keep as my last resort to handle this)?
Any pointers are appreciated!!
-Priyank

`hi,
u hav after event in dat select--> sap_end_of_job
in job start conditons or esle u can check start condition in extended job selection.
read the usage tip there..

Error in tabstrip control progtram while in Background job scheduling

Hi ABAPer's,
I need some help...I developed one tabstriip control program with 3 tabs. while excute it in foregroung it is executing nice..but while i am job scheduling the same program in background it was getting error's like .........
Control Framework: Fatal error - GUI cannot be reached
SET SCREEN not allowed in subscreens (screen: <Report Name> 0100)
so..if any body know the solution ...plz help me...
Thanks & Regards
Srinivas-SAP,

Hi,
please go through the functionality of tabstrips.
basically they are placed on tabstrips.
so they dont have their own ok codes and call screen and set screen ( to best of my knowledge )
can not be used.
if you are using set screen remove them.
even without using set screen if you are gettig the error, please let us know.
regards
Ramchander rao.K

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
Scheduling Background Jobs:
1.        Background jobs are scheduled by Basis administrators using transaction SM36.
2.        To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3.        While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e.        Department u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1.        To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2.        To access a particular jobu2019s output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3.        Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1.        Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of u201CScheduling background jobsu201D section).
Access to reportu2019s output:
1.        A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2.        The selection screen can be configured by clicking u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
fields).
3.        The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D section above).
4.        Upon entering selection criteria, the user clicks the Execute button   to
retrieve the list of matching spool requests.
5.        From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a.        Click the Print button   to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Error occured while posting the job schedule for JDBCAdapter

Hi Experts,
In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
#/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
#J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
#Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
Frequently are created Lock's and I need remove them in Visual Admin.
Any idea about this error?
Tks in advance.

Hi,
After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
Any ideas?
Thanks in advance.

SCSM 2012 - Setting Cube Job Schedule

Similar Messages

Maybe you are looking for