03-12-2009
SAS running audits
I'm not sure if anyone can help here. I don't know much about Unix but will give the information that I can.
I am trying to run audits of my data with the command sas audit. When it asks for a batch number I put in the number that I am looking to print.
When I do this I am getting the following error
/bin/ksh: bvalue..lst: not found
It then prints out the last batch that I ran audits for.
Sorry about the confusion but like I said I don't know anything about Unix. If anyone can help it would be greatly appreciated.
Thanks
9 More Discussions You Might Find Interesting
1. Cybersecurity
It appears there is alot of talk about different utilities that will pull data from PACCT files, sulogs, loginlogs, etc and put it in a format that is easy to read from multiple systems. Has anyone used or recommend any of these? I need to keep track of security on multiple systems running Non-Stop... (3 Replies)
Discussion started by: breigner
3 Replies
2. Shell Programming and Scripting
I need some help on sas on unix....
Is there any way to validate date in sas (1 Reply)
Discussion started by: radhika03
1 Replies
3. Shell Programming and Scripting
Hi,
I am executing the SAS program using Unix script to call SAS program, but i would like to run that SAS program in forground mode, does anyone know what is command.
Thanks in advance!! (0 Replies)
Discussion started by: terala
0 Replies
4. UNIX for Advanced & Expert Users
Does anyone had perfomed a tuning with SAS on Solaris???
Performance is not so good and I found out that Share Memory an Semaphores are the same that initial instalation, I havent found info at internet
Please help (1 Reply)
Discussion started by: alex blanco
1 Replies
5. Solaris
Hi, I have a solaris box with an LSI SAS HBA and a16 bay SAS JBOD. I can only see 15 of the 16 drives, ID 7 is not seen. Do I have to edit the st.conf file to get things to work properly?
Thanks (0 Replies)
Discussion started by: montanye
0 Replies
6. UNIX for Dummies Questions & Answers
HI all,
I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting.
My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder.
If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies
7. BSD
Dear all
My FreeBSD is version 4.11,
I want to enable audit,
Can anyone has a step by step document ?
In FreeBSD.org I see the doc look like need recompile kernel?
Is it really..?
Thanks and happy new years. (0 Replies)
Discussion started by: nnnnnnine
0 Replies
8. Red Hat
Hi All,
I am running SAS 9.2 on Red Hat Enterprise Linux 6.2 x86_64. At different stages in different programs I get the error below, which prevents my programs from running successfully:
ERROR: Error closing file. File =. System Error Code = 5.
I have almost no experience with Linux... (0 Replies)
Discussion started by: bgg
0 Replies
9. Linux
I bought for backup this controller
LSI LSI9212-4i4e 6G SAS
I will buy a quantum reader like this
Quantum TC-L62BN-EM 2500GB LTO
Two simple question
a)I read..2500GB,this mean i cannot use tape lto6 over 3tb?
b)Wich external cable?A sata external cable is good?
Thanks (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
LEARN ABOUT DEBIAN
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)