There must be something amiss with your "LD_LIBRARY_PATH" shell environ. Try:
... in your login shell and as the first line in your shell script to compare the values.
Secondly, search your system for the file:
And add that directory path to your LD_LIBRARY_PATH variable.
Oh. And failing that, check the search permissions on directories, and read permissions on the libraries.
Hi, how can i use unix shell command to get the autosys commands
for a set of given jobs?
autorep -J EMP% -w
returns all autosys jobnames starting with EMP and runtimes
However, i also want to see the autosys 'command' corresponding to the above jobs.
I don't want to sql query the... (1 Reply)
Hi there,
my problem is, that i need to get all jobs with status from a autosys instance.
If I use
autorep -J ALL -d >joblist.txt
longer Jobnames will be cut and the end will be replaced by 3 points like this
"ThisIsALongerJobNameAnd..."
If i try a single job query like
... (7 Replies)
hi,
i have autosys installed on unix.
i use "autorep -j t8i%" command to see the scheduled jobs. now i have changed some of the jobs and saved them too.
i gave the command jil< filename.jil to again insert the jobs. but my problem is what is the command to run all the jobs again so that i... (8 Replies)
Hi,
When i tried to run a job on autosys which has to run a command on sys1 but its
giving some other Machine name (sys56) , attempts ten times and fails. I would like to know from where this Machine column of autorep command gets input so that i
can change to correct Host Machine (sys1) and... (4 Replies)
Hi,
I am using AUTOSYS GUI based tool. But I want to get the job status from the UNIX command prompt.
1. I want to execute only autorep command in the UNIX command prompt.
If need to execute this command what are the settings need to do that.
2. Is it possible for executing this... (5 Replies)
Hi,
How to get correct field/column from autosys autorep command. I'm using GNU/Linux
I'm trying to get the difference of last end and last start and the status (ST).
In awk, i get the following excluding the heading part
$1 - jobname
$2 - Last Start date
$3 - Last Start time
$4 - Last... (1 Reply)
Hi,
I have written a ksh script and I'ma using the following command in it:
autorep -j %abcd% | grep RU | grep BOX1
The script works fine when executed manualy on the command prompt. But does not work when scheduled in crontab. I could see the following in the crontab log:
... (1 Reply)
Hi,
The user "MadeInGermany" tried to help on the below post by saying "This has been asked before; see the links below.
Get your current LD_LIBRARY_PATH and redefine that in your ksh script!
"
Thanks for the help. but this did not help. And my post got locked. I can't reply on my previous... (5 Replies)
Hi All,
I am using a putty session to login a server in which autosys is installed. we get the GUI by entering . /opt/CA/UnicenterAutoSysJM/autouser/autosys.ksh.server and then jobscape.
when i tried autorep -j jobname it gives me autorep not found. Please help me with this. (1 Reply)
Hi,
Is there any specific command to use to check only say Running jobs via autorep or similar command for Autosys? (0 Replies)
Discussion started by: sidnow
0 Replies
LEARN ABOUT DEBIAN
platform::shell
platform::shell(3tcl) Tcl Bundled Packages platform::shell(3tcl)__________________________________________________________________________________________________________________________________________________NAME
platform::shell - System identification support code and utilities
SYNOPSIS
package require platform::shell ?1.1.4?
platform::shell::generic shell
platform::shell::identify shell
platform::shell::platform shell
_________________________________________________________________DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.
This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
requirement is that the other shell (identified by its path), is actually executable on the current machine.
While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell
this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.
For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed
packages, versus the architecture of the shell running the repository software.
COMMANDS
platform::shell::identify shell
This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.
platform::shell::generic shell
This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.
platform::shell::platform shell
This command returns the contents of tcl_platform(platform) for the specified Tcl shell.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform::shell 1.1.4 platform::shell(3tcl)