Computer Associates BABWBN2900E20 Clients Agents Guide - Page 60

Activity Logs on Computers Running the AS/400 Enterprise Option, Activity Logs, Client Agents Guide

Page 60 highlights

Activity Logs Activity Logs on Computers Running the AS/400 Enterprise Option The Enterprise Option for AS/400 creates a log file in the CA ARCserve Backup library. The two file members are: ■ AGENT.MBR, which records the activities and errors relating to agent operations ■ ASBR.MBR, which records information on CA ARCserve Backup browsing activities Activity Logs on Computers Running the OpenVMS Enterprise Option As soon as the agent begins running on the server, CA ARCserve Backup generates an activity log file named aso$agent_.log, and stores it in the logs directory. A new log file-identified by sequential job number, date, and time- is created for each job and every subsequent startup of the agent. The content of each log file is determined by the level of tracing enabled on the agent. 60 Client Agents Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69

Activity Logs
60
Client Agents Guide
Activity Logs on Computers Running the AS/400 Enterprise Option
The Enterprise Option for AS/400 creates a log file in the CA ARCserve Backup
library. The two file members are:
AGENT.MBR, which records the activities and errors relating to agent
operations
ASBR.MBR, which records information on CA ARCserve Backup browsing
activities
Activity Logs on Computers Running the OpenVMS Enterprise Option
As soon as the agent begins running on the server, CA ARCserve Backup
generates an activity log file named aso$agent_<nodename>.log, and stores it
in the logs directory. A new log file
identified by sequential job number, date,
and time
is created for each job and every subsequent startup of the agent.
The content of each log file is determined by the level of tracing enabled on the
agent.