× 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.



We use option 1. Our startup program does the MKDIR for all the SMB shares we need to access.

Chris Bipes
Director of Information Services
CrossCheck, Inc.

707.665-2100, ext. 1102
707.793.5700 FAX
chris.bipes@xxxxxxxxxxxxxxx
www.cross-check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information.  If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited.  If you have received this e-mail in error, please immediately notify me by e-mail (by replying to this message) or telephone (noted above) and permanently delete the original and any copy of any e-mail and any printout thereof.  Thank you for your cooperation with respect to this matter.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jason Aleksi
Sent: Thursday, June 3, 2021 9:24 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Best practice for establishing a QNTC path

I am looking for a better solution or a preferred best practice for establishing a QNTC path from our IBM i to a Windows File Share, each being on a different LAN subnet?



*Current Problem*

Our IBM i resides on a 192.168.0.0/24 subnet. Our new Windows File Server is on a 10.0.0.0/23 subnet. Both can ping and talk to each other. There are no firewalls between, just routing/networking. As I understand, QNTC will broadcast out to dynamically find its Network Neighbors (via network broadcast). However, with the new 10.0.0.0 subnets, the Dynamic Discovery broadcasts do not make it to the new servers due to the broadcast domain.



If we manually create the QNTC path using MKDIR DIR(‘/QNTC/server’), everything works as it should (stream files, copies, etc.). However when the system IPLs, manually created QNTC paths are wiped out; thus the need to be recreated.



*Possible Solutions*

1) Create a CL script that runs MKDIR DIR(‘/QNTC/server’) for each
remote file server as part of the startup IPL sequence.



2) Modify each CL/RPG program to check/create the link each time:
MKDIR DIR(‘/QNTC/server’)
MONMSG CPFA0A0 /* Ignore if object already exists */



Are there any other methods or preferred best practices?



-JA-
--
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.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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.