Reviewing Request Times/Status and System Defaults › Listing System Definitions and Defaults (CONFIG) › Output Definitions

Output Definitions

The server displays the following types of information on your terminal:

AUTOLOG RETRY INTERVAL IS 30 SECONDS.

If you are logged on when a scheduled request runs on your user ID, the server checks every 30 seconds to see if you logged off. If you are still logged on, the server sends you a message.

PURGING IS DONE 5 DAYS AFTER REQUEST COMPLETION.

After you cancel a request, or it runs for the last time, information about the request remains in the server database for five days. Until then, you can use QUERY to check the status of the request, and you can update the request.

DEFAULT LATE INITIATION TIME LIMIT IS 00:02:00.

If a request cannot run at its scheduled time because you are logged on or the system is down, the server keeps trying to run it for 2 minutes after the original time. Then it skips that run of the request. You can override this behavior by using WITHIN when you schedule the request with SCHEDULE or EXEC.

DEFAULT INITIATION TIME IS 00:00:05 AFTER SCHEDULING.

If you do not use AT or FROMTIME in your SCHEDULE or EXEC command, the request first runs 5 seconds after you enter the command. The delay time applies only to requests scheduled to run today. For example, at 11:00 today you schedule a request to run tomorrow without specifying the start time, the server schedules the request to run tomorrow at 11:00:00, instead of 11:00:05.

SHIFT ‘FIRST’ IS BETWEEN 06:00:00 AND 16:00:00.

Your site has a shift named FIRST that runs from 6 a.m. to 4 p.m. every day.

RANGE ‘HOLIDAY’ IS BETWEEN 01/01/02 00:00:00 AND 01/02/02 23:59:59.

RANGE ‘HOLIDAY’ IS BETWEEN 11/26/02 00:00:00 AND 11/27/02 23:59:59.

RANGE ‘HOLIDAY’ IS BETWEEN 11/27/02 00:00:00 AND 11/28/02 23:59:59.

RANGE ‘HOLIDAY’ IS BETWEEN 12/25/02 00:00:00 AND 12/26/02 23:59:59.

Your system has a range named HOLIDAY that includes New Year’s Day, Thanksgiving, the day after Thanksgiving, and Christmas.

MON IS DEFINED AS A BUSINESS DAY.

TUE IS DEFINED AS A BUSINESS DAY.

WED IS DEFINED AS A BUSINESS DAY.

THU IS DEFINED AS A BUSINESS DAY.

FRI IS DEFINED AS A BUSINESS DAY.

SAT IS DEFINED AS A WEEKEND DAY.

SUN IS DEFINED AS A WEEKEND DAY.

Your system considers Monday through Friday as business days. Saturday and Sunday are weekend days.

THE RANGE FOR ‘QUARTER1’ IS BETWEEN 01/01/yy AND 03/31/yy.

THE RANGE FOR ‘QUARTER2’ IS BETWEEN 04/01/yy AND 06/30/yy.

THE RANGE FOR ‘QUARTER3’ IS BETWEEN 07/01/yy AND 09/30/yy.

THE RANGE FOR ‘QUARTER4’ IS BETWEEN 10/01/02 AND 12/31/02.

The quarters at your site are the traditional ones that start at the beginning of January, April, July, and October.

THE CLASS ‘A’ AUTOLOG LIMIT IS 3; WARNINGS WILL NOT BE SENT.

RESOURCE LIMITS ARE CPU 0, SIO 0, AND UIO 0.

MAXIMUM AUTOLOG RETRY ATTEMPTS IS 2 PER REQUEST.

Only three requests can run in class A at a time. After that, other requests wait until one original request finishes. The class has no resources limits.

The server does not try to autolog users who log on when a scheduled request runs. Therefore, CLASS requests for logged-on users requeue immediately. In this case, the servers attempts to start the request two times. After the attempts, the server skips the request. The server does not warn users that it is trying to autolog their user IDs.

CA VM:Schedule IS INITIATING ALL REQUESTS.

CA VM:Schedule is processing requests normally.

USERS MAY CHOOSE TO USE THE REQUEST EXECUTION MONITOR.

THE DEFAULT IS NO.

Users can choose whether to use the CA VM:Schedule request execution monitor. By default, the system does not use the request monitor.