AS400 Backup Job Submitted but not run

165 pts.
Tags:
AS/400
AS/400 backup
AS/400 jobs
Backup
DSPLOG
I have setup my AS400 to run weekly backups. But all that happens is the job gets queued and is subsequently never run. 
I have backup jobs on queue for last couple months. I have even changed the backup setting so that I am sure the selected library is not in use, but still the backup never runs. In dsplog it shows the backup job submitted but thats it. 
Any help will be appreciated. 
Thank you.

Answer Wiki

Thanks. We'll let you know when a new response is added.

if the jobs are still in the queue, as i understand that they are, you need to make certain that your jobq is attached to a subsystem that is active.

i would kill all of the back-up jobs before you do this, so they dont all submit and start up at the same time, or keep going active one job at a time.

-sarge

Discuss This Question: 27  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • CharlieBrowne
    If the queue is attached to a subsystem, check to make sure the jobs were not submiited either ON HOLD or for some distant scheduled time.
    41,380 pointsBadges:
    report
  • As400novice
    The current status of the job (QEZBKTMMON) is RLS i.e. it is not attached to a subsystem. Under work with subsystem descriptions, only QBASE is listed but QEZBKTMMON is not attached to it. So now I ask, please tell me how to attach this job to the active subsystem QBASE. Thank you.
    165 pointsBadges:
    report
  • As400novice
    Also, the job QEZBKTMMON was submitted to job queue QBATCH in library QGPL.
    165 pointsBadges:
    report
  • Batman47
    Sounds like you are using defaults.... QBASE is your controlling subsystem that runs interactive and QBATCH job queue is for batch jobs like your backup. There is also a batch subsystem called QBATCH. That should be started and it sounds like you don't have much started at all. What is the status of QBASE? It should be DEQW.
    1,050 pointsBadges:
    report
  • As400novice
    Yes we are using defaults. Under the menu WRKSBS, the following subsystems are listed: QBASE, QSERVER, QSPL, QSYSWRK, QUSRWRK. Under display subsystem description, QBASE is listed as status: active. However, under the command WRKJOBQ, QBASE is listed with 0 JOBS but QBATCH is listed with 10+ jobs ... all are backup jobs which are queued but not running. I don't understand.
    165 pointsBadges:
    report
  • As400novice
    i.e. under WRKJOBQ, the Job Queue is QBATCH and Subsystem is also QBATCH, but the backup jobs are just being queued without being run.
    165 pointsBadges:
    report
  • Splat
    Attaching your QBATCH job queue to your QBASE subsystem would not be advisable. I'd suggest modifying your system startup procedure by adding a STRSBS for QBATCH.
    7,625 pointsBadges:
    report
  • TomLiotta
    Attaching your QBATCH job queue to your QBASE subsystem would not be advisable. Why not? That's the default configuration. When running under QBASE, you don't normally have the QBATCH subsystem also running. That partially negates the point of using QBASE in the first place. Tom
    125,585 pointsBadges:
    report
  • Splat
    I don't think running the default configuration is advisable either. There's a QBASE job queue if you insist on running the jobs in that subsystem.
    7,625 pointsBadges:
    report
  • TomLiotta
    I don’t think running the default configuration is advisable either. To me, that implies not running QBASE at all; but instead running under QCTL or a similarly configured controlling subsystem environment. QBASE is intended for simple environments where no experience exists for work management. I wouldn't change a QBASE configuration because I want to keep a simple work environment available at all times. (I also never run a QBASE environment except in special circumstances such as recovering configurations.) There’s a QBASE job queue if you insist on running the jobs in that subsystem. True, and it might be advisable for backup jobs. Or not. The QBASE *JOBQ is and should be multi-threaded. Basic user backups and possible related jobs might need to run through a single-threaded *JOBQ like QBATCH, not QBASE. Without knowing what the backups are, it's hard to tell. Basic non-system backups might be best single-threaded. System backups will possibly be restricted state and have special handling. Standard GO BACKUP weekly backups include user libraries, documents and folders. Libraries such as QSYS are not part of it. Having QBATCH occupied with the backup is probably a good idea in a simple site. But you never know from the outside. Tom
    125,585 pointsBadges:
    report
  • Znason
    What are you backing up? Is this a save 21 option? Do you have BRMS?
    460 pointsBadges:
    report
  • As400novice
    [...] AS/400 Backup Job Submitted but not run [...]
    0 pointsBadges:
    report
  • As400novice
    Its a normal weekly backup not a save 21. This is not a system backup... its just a standard backup of certain database files. Even when I run strsbs QBATCH, the backup does not run.
    165 pointsBadges:
    report
  • Splat
    As400novice, execute a WRKJOBQ with no parameters to see which job queues are connected to which subsystems and determine the status of the job queue. It is possible that the job queue is not attached to a subsystem; it is also possible that the job queue is held.
    7,625 pointsBadges:
    report
  • As400novice
    Executing WRKJOBQ shows various queues (QBASE, QFNC, QINTER etc), all with 0 jobs. EXCEPT for job queue QBATCH in lib QGPL, which has 6 jobs in subsystem QBASE with status RLS. All jobs are backup jobs that are not being run. These jobs are NOT held.
    165 pointsBadges:
    report
  • OldSysAdmin
    I think you'll need to define in detail "normal weekly backup". In my experience, many shops don't use the backups from IBM menu options, but have their own CL programs or use BRMS. So you need to show each detailed step used to "run" (or generate) these normal weekly backups as you call them.
    945 pointsBadges:
    report
  • Splat
    Is the job queue held (not the jobs in the queue, but the queue itself)? If not, would you execute WRKSBSD for the QBASE subsystem & look at the job queue entries, posting the results here?
    7,625 pointsBadges:
    report
  • Lovemyi
    Is the jobq QBATCH attached to a subsystem? When you do a WRKJOBD do you see this - Queue Library Jobs Subsystem Status QBATCH QGPL 0 QBATCH RLS where the jobq is attached to a subsystem. In this case QBATCH jobq is attached to the subsystem QBATCH. If the subsystem field is blank then it is not attached and you need to probably start the QBATCH subsystem. But first I would go into the jobq qbatch and put the jobs on hold so they do not all try to run at the same time. Lovemyi
    2,310 pointsBadges:
    report
  • Batman47
    i.e. under WRKJOBQ, the Job Queue is QBATCH and Subsystem is also QBATCH, but the backup jobs are just being queued without being run. Executing WRKJOBQ shows various queues (QBASE, QFNC, QINTER etc), all with 0 jobs. EXCEPT for job queue QBATCH in lib QGPL, which has 6 jobs in subsystem QBASE with status RLS. All jobs are backup jobs that are not being run. These jobs are NOT held. Sounds like you need to look at what's running in QBATCH & QBASE since it's not clear where they are running from. WRKACTJOB SBS(QBATCH QBATCH) See if you have anything in MSGW status. If so, take an option 7 to see what the message is and have the problem corrected.
    1,050 pointsBadges:
    report
  • Batman47
    I meant WRKACTJOB SBS(QBASE QBATCH)
    1,050 pointsBadges:
    report
  • TomLiotta
    Even if the jobs are not held, the *JOBQ itself might be held. Even if the *JOBQ might be released, the maximum number of jobs from that *JOBQ might already be active. Even if the maximum number of jobs from QBATCH are not already active, the maximum number of jobs allowed to be active in QBASE might already be reached. Even if the maximum QBASE jobs aren't active, the subsystem might be in END status. Technically, we don't even know if QBASE is the controlling subsystem yet. Just because QBASE is active doesn't make it the controlling subsystem. The system controlling subsystem is configured elsewhere. For the most part, we don't know anything about the state of the system nor of its configuration. Run the WRKSBS command. Press F11=Display system data. Copy/paste the text from the resulting screen here. (Please select the text after pasting and click the {code} box above the entry area.) That will give us a start at asking the right questions. Tom
    125,585 pointsBadges:
    report
  • As400novice
    Is the job queue held (not the jobs in the queue, but the queue itself)? If not, would you execute WRKSBSD for the QBASE subsystem & look at the job queue entries, posting the results here? Spat Under WRKJOBQ, the job queue QBATCH has status RLS
                               Display Job Queue Entries                            
                                                                 System:   S652F46B 
     Subsystem description:   QBASE          Status:   ACTIVE                       
                                                                                    
      Seq  Job                       Max   ---------Max by Priority----------       
      Nbr  Queue       Library     Active   1   2   3   4   5   6   7   8   9       
       10  QBATCH      QGPL             1   *   *   *   *   *   *   *   *   *       
       50  QINTER      QGPL        *NOMAX   *   *   *   *   *   *   *   *   *       
      100  QCTL        QSYS        *NOMAX   *   *   *   *   *   *   *   *   *       
      150  QS36MRT     QGPL        *NOMAX   *   *   *   *   *   *   *   *   *       
      200  QS36EVOKE   QGPL        *NOMAX   *   *   *   *   *   *   *   *   *       
      250  QBASE       QGPL        *NOMAX   *   *   *   *   *   *   *   *   *       
                                                                                    
    Is the jobq QBATCH attached to a subsystem? When you do a WRKJOBD do you see this - Queue Library Jobs Subsystem Status QBATCH QGPL 0 QBATCH RLS where the jobq is attached to a subsystem. In this case QBATCH jobq is attached to the subsystem QBATCH. If the subsystem field is blank then it is not attached and you need to probably start the QBATCH subsystem. But first I would go into the jobq qbatch and put the jobs on hold so they do not all try to run at the same time. Lovemyi Under WRKJOBD I don't see that display (not even those headings), instead this is what I see
                               Work with Job Descriptions                           
                                                                                    
     Type options, press Enter.                                                     
       1=Create   2=Change   3=Copy   4=Delete   5=Display                          
                                                                                    
              Job                                      Job                          
     Opt  Description  Library                Opt  Description  Library             
                                                                                    
          QBATCH       QGPL                                                         
    
    Sounds like you need to look at what’s running in QBATCH & QBASE since it’s not clear where they are running from. WRKACTJOB SBS(QBATCH QBATCH) See if you have anything in MSGW status. If so, take an option 7 to see what the message is and have the problem corrected. POSTED: DEC 1, 2010 9:57 PM (GMT) I meant WRKACTJOB SBS(QBASE QBATCH) Batman Under WRKACTJOB SBS(QBASE QBATCH), nothing has the status MSGW
     Work with Active Jobs                     S652F46B 
                                                                 02/12/10  14:16:50 
     CPU %:    1.3     Elapsed time:   00:11:27     Active jobs:   107              
                                                                                    
     Type options, press Enter.                                                     
       2=Change   3=Hold   4=End   5=Work with   6=Release   7=Display message      
       8=Work with spooled files   13=Disconnect ...                                
                                                                                    
     Opt  Subsystem/Job  User        Type  CPU %  Function        Status            
          QBASE          QSYS        SBS      .0                   DEQW             
            CADSP04      JOHANN      INT      .0  PGM-JOBPRT       DSPW             
            CADSP05      MAFE        INT      .1  PGM-JOBPRT       DSPW             
            CADSP06      BUHLE       INT      .0  PGM-JOBPRT       DSPW             
            DSPKAV       KAVISH      INT      .0  CMD-WRKACTJOB    RUN              
            LANCHECK     QPGMR       BCH      .0  DLY-480          DLYW             
            QSYSSCD      QPGMR       BCH      .0  PGM-QEZSCNEP     EVTW
    Run the WRKSBS command. Press F11=Display system data. Copy/paste the text from the resulting screen here. (Please select the text after pasting and click the {code} box above the entry area.) Tom, Under WRKSBS this is what I get,
    Work with Subsystems                              
                                                                 System:   S652F46B 
     Type options, press Enter.                                                     
       4=End subsystem   5=Display subsystem description                            
       8=Work with subsystem jobs                                                   
                                                                                    
                           Total     Subsystem  Active                              
     Opt  Subsystem     Storage (M)   Number     Jobs   Status                      
          QBASE                 .00   383492       13   ACTIVE                      
          QSERVER               .00   383516       15   ACTIVE                      
          QSPL                  .00   383515        2   ACTIVE                      
          QSYSWRK               .00   383493       36   ACTIVE                      
          QUSRWRK               .00   383517        6   ACTIVE                      
          Q1PGSCH               .00   383538        1   ACTIVE 
    165 pointsBadges:
    report
  • Splat
    From what you've posted, I suspect that the maximum number of jobs allowed from the QBATCH job queue has been reached. If you would, try CHGJOBQE SBSD(QBASE) JOBQ(QBATCH) MAXACT(2) - if your queued jobs start moving into QBASE, that was the chokepoint. If that doesn't work, you might consider increasing the maximum jobs in the subsystem (CHGSBSD SBSD(QBASE) MAXJOBS(n+1)).
    7,625 pointsBadges:
    report
  • TomLiotta
    LANCHECK     QPGMR       BCH      .0  DLY-480
    That job seems suspicious. If it was submitted through QBATCH, then no other jobs are going to run until it finishes. Its name and the DLYJOB function suggest a program that periodically wakes up to do some LAN-related check. If so, it probably would be better to submit it through the QBASE *JOBQ. If it wasn't submitted through QBATCH, then it can probably be ignored for now.
    QBASE                 .00   383492       13   ACTIVE
    
    The system says 13 jobs are in QBASE, but WRKACTJOB SBS(QBASE QBATCH) only shows six jobs. Seven other jobs aren't shown. They're likely in some suspended status. Please run WRKACTJOB SBS(QBASE QBATCH) again; but this time press F14=Include. That will ensure that temporarily suspended jobs will also be shown. Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    Also, if you have run the CHGJOBQE SBSD(QBASE) JOBQ(QBATCH) MAXACT(2) command, you should return the MAXACT() value back to (1). It's a good temporary (very) test to see what the problem might be, but it's very likely that you don't want the setting left that way. It might be better simply to check attributes of jobs such as LANCHECK to see if they came in through QBATCH. No need to change a system setting when you can just look at the right attributes. Tom
    125,585 pointsBadges:
    report
  • As400novice
    [...] AS400novice has everyone on board helping him figure out why the AS/400 backup job is submitted but not running. Check out what Rudedog, CharlieBrowne, Splat, TomLiotta, Znason, OldSysAdmin, Lovemyi, and [...]
    0 pointsBadges:
    report
  • As400novice
    [...] AS/400 Backup job submitted but not running [...]
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following