Sponsored Content
Operating Systems AIX Autosys remote agent installation issue Post 302553856 by hidnana on Friday 9th of September 2011 03:12:00 AM
Old 09-09-2011
Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.

But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.

It would really help to know if these 2 schedulers can exist in the same Unix server and anything specific need to be done to achieve the same.
 

10 More Discussions You Might Find Interesting

1. AIX

VIO server support and agent installation

Hi All, I have the following 2 questions: I can't seem to find which versions of VIOserver are supported by IBM. and if there are rule for installation of tooling (e.g. monitoring agents) on a VIOserver. thanx in advance >Raba (3 Replies)
Discussion started by: raba
3 Replies

2. UNIX for Advanced & Expert Users

installation entirely remote - Solaris

moved to Solaris... https://www.unix.com/sun-solaris/84558-installation-entirely-remote-solaris.html (0 Replies)
Discussion started by: vbe
0 Replies

3. UNIX for Advanced & Expert Users

Autosys Issue

Hi Guys.. This is Mahesh.. Actually I have to work with autosys... Can anyone tell me how to start Autosys in the command prompt of Linux(fedora 8)? And from where can i download autosys software (2 Replies)
Discussion started by: mraghunandanan
2 Replies

4. UNIX for Advanced & Expert Users

Issue while killing the process using autosys job

Hi, I have one autosys job that will retrieve the proccess id's and will kill those processess as follows, pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'` kill -9 pid but after executing this particular job, its status is showing as TE(terminated) and the kill process is... (3 Replies)
Discussion started by: Kattoor
3 Replies

5. UNIX and Linux Applications

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

6. UNIX for Advanced & Expert Users

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

7. Infrastructure Monitoring

Agent Installation Issue on Ops Center

Hi guys . While installing the agent on an asset Solaris system: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies

8. Shell Programming and Scripting

Autosys job scheduling issue,

Hi Friends, There is an Autosys scheduled job that runs on the second day of the month, and it is using the Business day calendar. So when the month starts on a weekend or there is a holiday at the beginning of the month the second business day and second day of the month obviously do not... (1 Reply)
Discussion started by: Aditya_001
1 Replies

9. Red Hat

Issue with Isilon and Autosys

We are testing NFS Isilon mounts with autosys jobs. We continue to receive an autosys profile not found error. We have confirmed the profile file exists and can be referenced by the ID being used. Autosys remote agent process is able to recognized and see the command section (command to be... (2 Replies)
Discussion started by: John Gillis
2 Replies

10. Red Hat

Autosys 4.5 installation

Hi Folks, we are trying to install autosys4.5 on RHEL 7 Environment (Support to autosys 4.5 is stopped around 2014) but we are installing with extended approval. need help on installing the application on the new enviornment from solaris. could someone please help or share me the installation... (0 Replies)
Discussion started by: somarbc
0 Replies
rtsched(1)						      General Commands Manual							rtsched(1)

NAME
rtsched - execute process/lightweight process (LWP) with real-time priority SYNOPSIS
scheduler priority command [arguments] scheduler] priority scheduler] priority scheduler] priority DESCRIPTION
executes command with POSIX or HP-UX real-time priority, or changes the real-time priority of currently executing process (pid) or light- weight process (lwpid). All POSIX real-time priority processes or LWPs are of greater scheduling importance than processes/LWPs with HP-UX real-time or HP-UX time- share priority. All HP-UX real-time priority processes/LWPs are of greater scheduling importance than HP-UX timeshare priority pro- cesses/LWPs, but are of lesser importance than POSIX real-time processes/LWPs. Neither POSIX nor HP-UX real-time processes/LWPs are subject to degradation. POSIX real-time processes/LWPs may be scheduled with one of three different POSIX real-time schedulers: SCHED_FIFO, SCHED_RR, or SCHED_RR2. See rtsched(2) for details. is a superset of See rtprio(1). Options Specify the desired scheduler: POSIX real-time schedulers: SCHED_FIFO SCHED_RR SCHED_RR2 HP-UX real-time scheduler: SCHED_RTPRIO HP-UX timeshare scheduler: SCHED_HPUX SCHED_NOAGE Specify priority range; any integer within the inclusive priority range of the corresponding scheduler. is required for all schedulers except SCHED_HPUX. If scheduler is SCHED_HPUX, the priority argument is ignored. The default priority range of each scheduler is as follows: scheduler highest priority lowest priority -------------------------------------------------- SCHED_FIFO 31 0 SCHED_RR 31 0 SCHED_RR2 31 0 SCHED_RTPRIO 0 127 SCHED_NOAGE 178 255 SCHED_HPUX N/A N/A Higher numerical values for the priority represent higher priorities under POSIX real-time schedulers, whereas lower numeri- cal values for the priority represent higher priorities under HP-UX real-time and timeshare schedulers. Specify an already executing process ID (pid). Specify an already executing lightweight process ID (lwpid). The target LWP (lwpid) can be in any process. Select all the LWPs in an already executing process (specified with When scheduling policy is not specified explicitly using the option, the process's current schedul- ing policy will be used. If the requested priority value is in the range for this scheduling policy, the scheduling policy and priority of the process and all its LWPs will be changed to these values. Please note that it may cause the scheduling policy to be changed for some LWPs. If the user is not a member of a group having access and is not the user with appropriate privileges, command is not scheduled, or pid's/ lwpid's real-time priority is not changed. When changing the real-time priority of a currently executing process/LWP, the effective user ID of the calling process must be the user with appropriate privileges, or the real or effective user ID must match the real or saved user ID of the process to be modified. In presence of processor sets (see pset_create(2) for details), the application execution is restricted to processors in the application's processor set. The threads in different processor sets do not compete with one another for processors based on their scheduling policy and priority values. The scheduler looks only at threads assigned to a processor's processor set to choose the next thread to run. RETURN VALUE
returns exit status: if command is successfully scheduled or if pid's or lwpid's real-time priority is successfully changed; if command is not executable, pid or lwpid does not exist, or priority is not within the priority range for the corresponding scheduler; if command (pid/lwpid) lacks real-time capability, or the invoker's effective user ID is not a user who has appropriate privi- leges, or the real or effective user or the real or effective user ID does not match the real or saved user ID of the process being changed; or if rtsched encountered an internal error or if rtsched is not supported by this release. EXAMPLES
Execute file with SCHED_FIFO at a priority of 10: Execute file with SCHED_RTPRIO at a priority of 127 (this is synonymous to Execute file with the SCHED_HPUX scheduler: This is useful to spawn a timeshare priority command from a real-time priority shell. Set the currently running process, pid 24217, to execute with SCHED_RR2 at a priority of 20: Now change its priority to 10 using the same scheduler: Set the currently running LWP, lwpid 987312, to execute with SCHED_RR at a priority of 10: Set all currently executing LWPs in a process pid 21342 to execute with SCHED_FIFO at a priority of 25: WARNINGS
The priority values used by may differ from those used by other commands. For example, ps(1) displays the internal representation of pri- ority values. AUTHOR
was developed by HP. SEE ALSO
rtprio(1), setprivgrp(1M), getprivgrp(2), pset_create(2), rtprio(2), rtsched(2), _lwp_getscheduler(2), _lwp_setscheduler(2), pstat_getlwp(2). rtsched(1)
All times are GMT -4. The time now is 01:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy