Perform electronic vaulting. The vault dataset must already have been allocated and created. Refer the Installing Zebb for detailed information on electronic vaulting. Time interval at which to issue database " percentage full " warning messages.
Valid values are minutes. The default is 10 minutes. The captured IF blocks on Zebb's database are not used for IF statement evaluation or needed for restart processing. Zebb lets you control what functions are automated and to what degree. When Zebb is first installed, unless specified otherwise, jobs are assigned to Shadow coverage mode. You can change Zebb restart services such as:.
To change the default restart services. Default restart coverage mode for new jobs. This is assigned only if coverage is not specified when the job is defined. Code indicating the services Zebb is to provide to jobs, depending on the submission source of the job.
Provide production and restart services regardless of the job's source. This way Zeke will not track the job, but Zebb can restart it. Provide restart services regardless of the job's source; however, provide production services only to jobs controlled by automated scheduling packages. Provide production and restart services only to jobs controlled by automated scheduling packages. Code indicating whether to fail the job if no cause for rerun is supplied on the Job Restart Management screen.
Allow the operator to give the restart job a cause for restart or fail the job. Issue a WTOR for the operator to respond whether to fail or restart the job. Do not allow automatic restart services. Put the job on hold and apply a nonexecutable status. Code indicating the action to take if a non-gencycle Zebb job in restart status is submitted by Zeke with the same event and version numbers but a different schedule date than the job in restart status in Zebb.
If the Zeke-submitted job has a different schedule date, event number, or version number, this message displays:. This message identifies the Zeke and Zebb event and version numbers and schedule date and provides an opportunity to fail the job or restart it using the information in the Zebb database.
R - Restart. Restart the Zeke-submitted job using information from the Zebb database for the most recent job in restart status.
N - New. Create a new temporary gencycle for the Zeke-submitted job. This message displays on the console:. P - Production. Process the Zeke-submitted job as a new production run, re-using and overwriting the last production run for this job that is in restart status in the Zebb database. F - Fail.
Fail the Zeke-submitted job without processing it, leaving the last gencycle in restart status in the Zebb database. If the non-gencycle Zebb job in restart status is submitted by Zeke with a different schedule date, Zebb creates a temporary gencycle to process the incoming job, retaining the job in restart status in the Zebb database.
No manual intervention is required. Zebb does not change the job to a gencycle job, but leaves the gencycle count as displayed on the ISPF 1. Display message E48E32R only if the version number of the incoming Zeke job differs from the version number captured by Zebb when the job last executed. Display message E48E32R if the version number, event number, or schedule date of the incoming Zeke job differs from the information captured by Zebb when the job last executed.
Zebb does not perform maintenance on the GDG absolute dataset created in the failing job. Zebb performs maintenance on the GDG absolute dataset created in the failing job, if needed. Allow two additional appended step names on restarts. These second and third entries append two step names to the end of a job in restart status after the last step on the original execution , and rerun or restart the job. If the second and third entries each specify a valid step name, steps by those names also can be added to the restart after the last step of the original production execution.
Requires that the Zebb JES2 exits are installed. If you choose this option, the Zebb JES2 exits do not need to be installed. Allow resubmission of the job, regardless of the job's coverage mode. If the RSub-Conf option is also set to Yes, the operator must first confirm the resubmission. If the job is in Shadow, Dataset, Dsmaint, or None mode, display a message and do not resubmit the job. To resubmit the job, the coverage mode must first be changed to Restart.
These settings are valid for the current submission of the job only; they then revert back to their original settings according to the job definition and generation option values. The selected command format and the generation option must agree. See Selecting the Zeke Commands for more information. That means Zebb informs the operator of any NOTCAT-2 errors for all jobs defined in its database and waits for the operator's response. However, it does not provide Dataset-Not-Found protection.
Zebb protects but does not create records for jobs that are not defined to the Zebb database. Job and dataset protection are applied to dataset manipulation attempts. Zebb provides unique IMS dataset protect services. Code indicating the action to take when Zebb encounters dataset contention. The operator has these options: bypass the failure; fail the job; or retry the attempt to scratch the dataset. This helps to prevent logic errors and allows Zebb to attempt dataset maintenance against system datasets.
Zebb provides automatic SYS x dataset protection. Zebb does not provide automatic SYS x dataset protection. Code indicating whether extended generics are preferred for DSN Exempt screen entries. These rules apply:. Multiple node entries are allowed. Do not support extended generics for DSN Exempt screen entries.
An asterisk is not allowed in the first position of the DSN mask in the exempt table. Code indicating whether to recapture the GDG absolute number at step termination if it has changed since job start. Recapture the GDG absolute number at step termination, if it has changed since job start. The GDG absolute numbers captured at job initiation are retained in the Zebb database and used for restarts and reruns.
If another job creates a "plus one" GDG after this job starts but before the creating step in this job , then the GDG absolute number retained by Zebb will not be the same as created. If a Zebb-monitored job references a GDG dataset as input, but the specified generation does not exist, message E48F02E is displayed and the job is not allowed to execute.
The job is in production status P on Zebb's database. If the job is changed to restart status manually and a restart is attempted, the restart is disallowed and this message E48R28E is displayed. Zebb collects job execution history for jobs with the History Coverage mode. The history contains all data pertinent to every execution of a job, production as well as restart.
Zebb also provides a means of archiving and purging those history records. The criteria for the number of copies to retain and the number of days to keep the records can be defined by the user. When a record meets these criteria, it is purged from the database and moved to an archive dataset. This frees space in the database. When Zebb is installed, the default is to collect at least three execution history records and keep them for five days for every job defined with history coverage mode, if History days and copies are not specified when the job is defined.
The ARCHIVE command, which deletes old gencycles, recognizes the temporary gencycle job because its gencycle-count-to-keep is zero, but it has multiple gencycles. For jobs with temporary gencycles, the ARCHIVE command does not delete a gencycle which is in restart status as for normal gencycle jobs. For temporary gencycles, if one gencycle of the job is in restart status and there are others in DONE production status, the restart status cycle and the most current production gencycle are retained.
If deleted, you cannot rerun the last execution of the job. To change the generation options related to the archive process.
Note: 00 00 indicates no Archive or Autopurge will be done. Minimum number of production cycle history records up to characters long to retain in the Zebb database at all times rather than archiving them.
The default value is 3. The values for Histcpy and Histday are defaults that are applied at the time a job is defined to Zebb. These values are not used if specified by the job definition function. History records are generated only for jobs that have History Coverage set to Y. Number of days up to characters long a history record must be retained before it is eligible to be archived to a secondary dataset.
The default value is 5. The Histcpy requirement above must be exceeded before Zebb archives any records. For example, if Histcpy is 3 and Histday is 5, then at least 3 records will be retained online. During archiving, records older than 5 days are archived. If there are not at least 3 records younger than 5 days, the most recent 3 records are retained online regardless of their age.
If Autopurge is set to Y, Zebb purges job records from the database that executed on or before this date. Jobs that have not executed since this date are considered obsolete and are marked for automatic deletion by the next ARCHIVE execution. Code indicating whether Zebb is to automatically purge job records flagged as deleted. Allow Zebb to automatically purge deleted job records from the Zebb database. An Arctime value must be specified for this function to run automatically.
Code indicating whether Zebb is enabled to archive eligible history records from the database. Do not archive history records. The archive function will not run, manually or automatically.
Default is Make sure that the Arctime and Bkuptime generation options are not set to the same value. The archiver moves eligible history records to the dataset specified by the ARCDSN parameter and purges deleted job records. ASG recommends that Arctim2 be set to 12 hours later than Arctime.
Name of the archive dataset. This dataset can be either simple sequential or GDG. Refer to the Installing Zebb section for archive dataset allocation details. If the disposition is SHR, the dataset must be created before the archiver is activated for the first time. Archive dataset primary and secondary cylinder allocation size Required if the disposition is NEW.
This forces the operating system to release any enqueue it has on the archive dataset. The subtask is immediately re-initialized automatically.
Valid values are days. Zebb allows you to determine the default values for several system-related items such as the Zebb operator command prefix and whether to issue messages from dataset services. Display error messages for uncatalog and scratch attempts. To change the system default settings. To change the command prefix for operator commands, enter up to two characters not already reserved for use by another system. Default is an exclamation point!
This is the Zebb system that invokes the scheduling system interface and can issue scheduling commands, and it is also the system where Zebb Archive runs automatically. All systems sharing the same database should specify the same value. Eight-character default online operator ID. This is the ID Zebb uses when an unknown operator logs on to the Zebb online system.
Code indicating whether an unknown operator ID can log on to the Zebb online system. Allow unknown operator IDs to log on to the Zebb system. Code indicating whether to automatically assign the jobname as the user ID when a job is defined. Code indicating whether to write error messages showing return codes from the uncatalog and scratch attempts to the job log. Code indicating whether the informational message showing the dataset name to be scratched should be issued, alerting you of Zebb activity against the datasets.
Route codes to use for message routing. Specify codes in list form separated by commas or spaces, and enclosed by parentheses. You can enter up to six codes For example: 5,6, Enter the network registration ID. Do not broadcast; generate console command responses only for the console that issued the command. Track all started tasks that match an Auto Definition or Job Definition record. Maximum condition code status displayed by Statusview.
If a step receives a condition code greater than or equal to the maximum value, then the job is assigned a CCEND condition code end status. Code indicating whether to omit Auto-Add processing for a job already defined in the Zebb database. Skip Auto-Add processing. If a job matching the Auto-Add table already exists in the Zebb database, these job definition specifications are not changed:.
Code indicating whether to activate the Zebb server for OpsCentral. This enables Zebb to act as a server for the OpsCentral client. A user ID up to eight characters long that Zebb uses as a default on job add functions when a user ID is not otherwise specified. An application ID up to eight characters long that Zebb uses as a default on job add functions when an application ID is not otherwise specified.
A group ID up to eight characters long that Zebb uses as a default on job add functions when a group ID is not otherwise specified. Zebb provides external interfaces for vendors' or customer-created products. These interfaces require a user-coded program be created to transfer the data or actions generated by Zebb to the other product s. Zebb provides sample user exits which you can modify if necessary to conform to your unique computer environment.
For complete interface installation instructions, see the section on Zebb exits in the Installing Zebb. Also, included with these options are DASD migration software product interfaces.
SMF services could be interrupted or stopped when Zebb recalls a dataset migrated by one of these packages. The only reason Zebb recalls a migrated dataset is to scratch it, so these options prevent the retrieval of any migrated datasets.
To activate the interface options. Code indicating whether to activate the problem-tracking interface subtask within the Zebb address space. These are the valid values:. For complete installation instructions for this interface, see the section on Zebb problem tracking interfaces in the Installing Zebb. Code indicating whether to call the user's problem-tracking exit for jobs abending with S but using no CPU time.
Do not call the user's problem-tracking exit for jobs abending with S but using no CPU time. Call the user's problem-tracking exit for jobs abending with S but using no CPU time. Code indicating whether to activate the tape management interface within the Zebb address space.
For complete installation instructions for this interface, see the section on the Zebb tape management interface exit in the Installing Zebb. Code indicating whether to activate the scheduler interface subtask within the Zebb address space. For complete installation instructions for this interface, see the section on the Zebb scheduling system interface exits in the Installing Zebb. Code indicating whether you want to activate the DMS Distributed Management Server interface for product-to-product communications.
To activate the DASD migration product interface, enter one of these codes indicating the product you use. No other interface installation steps are necessary. Volume serial number that the DASD migration product is to use to determine if the dataset has been migrated offline. Code indicating whether to maintain compatibility with ThroughPut Manager, which enqueues DSNs for the life of a job by performing catalog activity under the TCB of the initiator's caller.
Code indicating whether to skip GDG index error messages at run time. Skip any GDG index error message at run time.
Required if the tape manager EPIC is on the same system. Zebb supports several interfaces. These generation options activate the SMF-related interfaces:. To set SMF user exit options. The exit is then called at execution time for each job that Zebb would track, auto-add, or exclude from tracking based on its presence in the Zebb database or Zebb auto-add table; the exit can be used to override the action Zebb would take otherwise.
You can track the reasons why a job is being restarted with the Cause For Restart field. This field is located on the Job Restart Management screen. If desired, you can set a generation option that requires a restart reason before a job can be resubmitted. See Changing Default Restart Services. The restart reason can be printed on reports, which is helpful for determining trends.
To help standardize the reason text, Zebb provides a facility for defining codes and descriptions. When a job fails, Zebb searches the Auto Cause data for a matching cause code. If one matches, Zebb automatically uses this text as the failure reason.
Also, if a user-assigned code is entered in the Cause For Restart field, the text is automatically displayed on the Job Restart Management screen if a matching entry is defined on the Auto Cause For Rerun Facility screen.
To define the cause codes and associated descriptions. Five-character system abend code. You must enter the exact code; generics are not supported. If a step does not complete successfully, Zebb determines if the code in this field matches the abend code. If a step does not complete successfully, Zebb determines if the code in the Cause Code field matches the abend code.
To enter your company name and address information. Zebb allows you to control the colors that display on your ISPF online screens. The color and attributes you choose only effect your logon ID and remain in place until you change them again. The command INIT resets the colors back to the default values. Code indicating the color to be used for each feature. Enter the first letter of the color name. Available colors are listed at the bottom of the screen. Mean systemic blood pressure was maintained between 40 and 45 mm Hg for 60 mins by withdrawal or re-infusion of blood as needed.
Afterward, efforts to control the blood pressure were discontinued, and the animals were continuously monitored for another 90 mins. Exhaled NO was monitored throughout the experiments using a chemiluminescense analyzer. Lung tissue samples were harvested at the end of the experiment and immediately frozen in liquid nitrogen. We performed Western blot analyses on the samples to compare iNOS protein concentrations between the two groups. The results were analyzed using t-tests and an alpha of 0.
We conclude that dexamethasone attenuates hemorrhagic shock-induced intrapulmonary formation of NO and that this attenuation may be mediated via transcriptional regulation of iNOS but not CAT We speculate that targeted suppression of iNOS with glucocorticoids might ameliorate direct tissue damage caused by NO overproduction and that measuring exhaled NO concentrations represents a useful means of monitoring therapeutic success.
Since its founding in , the Society's achievements have made it an important voice in American Medicine and the foremost advocate for all patients who require anesthesia or relief from pain.
Previous Abstract Next Abstract. Printable Version.
0コメント