|
I try to "seek first to understand, then to be understood". When it comes
to those SBMJOBs perhaps they were burned too often by people who always
changed the defaults to some other value which caused them issues? I
still wouldn't hard code it and I would use job descriptions. I would not
use standard values, like QDFTJOBD, but would use custom ones. And the
installation guide might say "we use these job descriptions and we have
these values on that job description, and WHY. With maybe some clause
that changing them is at your own peril. Maybe even a sample problem in
the trouble shooting steps that says "because you changed the job
description".
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
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 08/14/2018 03:39 PM
Subject: What's an iASP?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
That question was just asked of me by an OEM software vendor that is well
known and been in the AS/400/iSeries/System i/IBM i space for quite some
time. I was asking if the software they sell would run in an iASP so it
could be replicated by PowerHA.
Then I went on to discover that rather than use the job description
values,
in all of the software the values were hard coded into the various SBMJOB
commands in the software.
How do these guys stay in business?
If you are an OEM software vendor, at least try and keep up with the
terminology so you don't sound as ignorant as this one is. Better yet
support the new technology available. Clearly I will not identify the
company but geesh.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--
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
--
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 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.