Functionality The function module ARCHIVE_ADMIN_GET_JOB_INFO> determines jobsfor archiving runs and archive files. Using the parameterJOB_STATES>, you can delimit the status of jobs to be determined.The archving runs, archive files, job types for data archiving, and, ifrequired, user names are transferred to table INFO_REQUESTS>. Thejobs determined and their accompanying information are also returned inthis table. The last completed job is determined for a specific archiving run orarchive file and for a specific job type. If there is also an activejob, this information is also supplied. In this context, 'active'refers to jobs with the status 'planned', 'released' 'ready' or'active'. You can also make restrictions regarding the job status anduser.Description If the parameter JOB_STATES> is not specified or is blank, jobswithout restrictions are examined for their status. Otherwise, jobs aredetermined that have a status other than non-initial value for theparameter JOB_STATES>.Description Every entry in the table INFO_REQUESTS> specifies an archivingrun or an archive file and the accompanying job type defines which jobis to processed. The fields have the following significance:
- DOCUMENT>: Archicing run
- ARCHIV_KEY>: Archiing file (blank if a job is to be determined
for a specific archiving run)
- JOBTYPE>: Type of data archiving job
Permitted job types for an archiving run: WRI: Write job REL: Reload job FIN or END: Postprocessing job Permitted job types for an archive file: DEL: Delete job STO: Job to store files in a storage system RET: Job to retrieve files from a storage system IDX: Index construction/deconstruction
- EXT_USER >: Restriction of the job to be determined with regard
to the specified user name
- Structure TBTCO>: Job data determined
|