Re: node.js xmlservice issue -- WEB400

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

Subject: Re: node.js xmlservice issue
From: Bryan Dietz <bdietz400@xxxxxxxxx>
Date: Thu, 12 May 2016 08:43:46 -0400
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

In the cover letter for PTF SI59404

Abstract
Ship Node.js V4

CORRECTION FOR APAR SE63904 :
-----------------------------
Node.js V4 support.
Multiple Node.js versions can co-exist on a system. A script
nodever.sh is provided to set the effective version.

Its in the new directory
/QOpenSys/QIBM/ProdData/OPS/Node4/bin

Bryan

Bradley Stone wrote on 5/12/2016 8:13 AM:

Nice, Bryan. Thanks for the information. I'm going to look into that.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: node.js xmlservice issue , Bradley Stone

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.