Re: Dropping of /QNTC support for certain functions

+1
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Brad Stone
Sent: Thursday, October 17, 2024 5:23 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Dropping of /QNTC support for certain functions

I always tell customers to stay away from two folders.. QNTC and QDLS...
This won't break anything with SPLTOOL except for maybe a couple customers
out of thousands that probably use QNTC. I've already saved this link for
those that run into an issue. I may post it on FieldExit.com as well.

Also, SPLTOOL doesn't use IBM i Transformation services at all (not sure
if that was the suggestion?). It was creating PDFs many years before IBM
even had the idea. :)

On Thu, Oct 17, 2024 at 4:02 PM Paul Therrien via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Brad Stone - I wonder will this break SPLTOOL command SPL2STMF where
the target is '/QNTC/...'?

Paul

(BTW - we use SPLTOOL all over the place. Very happy with it.)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Rob Berendt
Sent: Thursday, October 17, 2024 4:00 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Dropping of /QNTC support for certain functions

IBM will be removing (not just unsupporting) support for /QNTC for
directly outputting reports from 5770-TS1 (IBM Transform Services for i).
This will happen for currently supported versions of the OS and not
just future releases. The MTU for said releases has been updated

accordingly.

So if you do stuff like
OVRPRTF FILE(QP1ARCY) DEVTYPE(*AFPDS) TOSTMF(&QP1ARCY) WSCST(*PDF)
and /QNTC was part of &QP1ARCY then store it local first and then CPY
it to QNTC.
Luckily we were already doing this. At least for our BRMS recovery
reports.
https://www.ibm.com/support/pages/node/6471617
n=ibm.com

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.