× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Forgot the NOT
Save While Active does NOT work for IFS, even though it exists.

SQL resulting in error.

select a.job_name, b.* from table(qsys2.job_info( JOB_USER_FILTER
=> 'PRODUCT')) a, lateral (select * from
table(qsys2.joblog_info(a.job_name)) x) b where (a.job_name like
'%BRMFULL05%' or a.job_name like '%BRMBRCCYCA%') and b.message_id
in('CPF3837', 'BRM14A1', 'BRM1413')
Query cannot be run. See lower level messages.

Job log not displayed or listed because job has ended.
User-defined function error on member QSQPTABL.
Cancel reply received for message CPF503E.

Message ID . . . . . . : CPF503E
Date sent . . . . . . : 05/01/18 Time sent . . . . . . : 13:18:09

Message . . . . : User-defined function error on member QSQPTABL.

Cause . . . . . : An error occurred while invoking user-defined function
JOBLOG_INFO in library QSYS2. The error occurred while invoking the
associated external program or service program QDBSSUDF2 in library QSYS,
program entry point or external name QSQJOBLOG, specific name QSQJOBLOG. The
error occurred on member QSQPTABL file QSQPTABL in library QSYS2. The error
code is 1. The error codes and their meanings follow:
1 -- The external program or service program returned SQLSTATE 42704. The
text message returned from the program is: JOB LOG NOT DISPLAYED BECAUSE JOB
COMPLETED EXECUTION .


Paul

From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Tuesday, May 01, 2018 12:39 PM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS IFS save start and end times - IFS locks

First of all I think your email had some typos or grammatical errors. Save while active on IFS is a sick joke.

Something like this then?
select a.job_name, b.*
from table(qsys2.job_info(
JOB_USER_FILTER => 'QUICK')) a,
lateral (select * from table(qsys2.joblog_info(a.job_name)) x) b
where (a.job_name like '%MONDAYEDD%'
or a.job_name like '%TUE_FRIEDD%')
and b.message_id in('CPF3837', 'BRM14A1', 'BRM1413');

[cid:image001.gif@01D3E14F.6DB1A120]

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com<http://www.dekko.com/>





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date: 05/01/2018 11:55 AM
Subject: BRMS IFS save start and end times - IFS locks
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
________________________________



I need to get some history for my BRMS IFS start and end times.
The 10 minute IFS save window varies from 23:30 thru 23:59.

The BRMS report PRTRPTBRM does not include IFS, so that won't work.
DSPLOG CPF3837 or BRM14A1 will give me end times.
DSPLOGBRM BRM1413 will give me start times.

I have a production job (5 minutes) that intermittently will fail due to BRMS save IFS locks.
The job needs to run as close to midnight as possible.
Save While Active is working fine for libraries.
Save While Active does work for IFS, even though it exists.

Some options on the table.
1) Create a monitor for the failure and automatically do a retry.
2) Create BRMS GUI omits for the IFS objects.
3) Add to the start of the scheduled job CHGATR OBJ *NO, then at the end of the schedule job CHGATR OBJ *YES.

Any thoughts from the group?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.