IBM offers Enterprise Extender on multiple platforms:
https://www.ibm.com/products/communications-server-for-data-center
- - - - - - - - - -
Timothy Sipples
I.T. Architect Executive
Digital Asset & Other Industry Solutions
IBM Z & LinuxONE
- - - - - - - - - -
E-Mail: sipp...@sg.ibm.com
-
Did you do this?
[V9.2.0 Jul 2020]BACKMIG( backward-migration-target-vrm )
The queue manager is to start up and perform backward migration actions
such that it can be restarted at the backward-migration-target-vrm, and then
the queue manager is to shut down without ever being available to any
Hi,
It might be helpful to include the output from the Job's/STC's JESMSGLG
(DSID 2).
Regards,
David
On 2021-07-28 19:20, Steely.Mark wrote:
I am trying to test the BACKMIG of MQ V9.2.
The directions says to use the START QMGR command.
For some reason I can't get this to work. To tired.
This
Visara? It's still around.
First Horizon Bank
Mainframe Technical Support
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, July 28, 2021 3:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Using Windows HIS to replace a mainframe Enterpr
I am trying to test the BACKMIG of MQ V9.2.
The directions says to use the START QMGR command.
For some reason I can't get this to work. To tired.
This is command I usually use to start the QMGR: +MQSI START QMGR
PARM(MQSIZPRM)
I did try this command: +MQSI START QMGR PARM(MQSIZPRM) BACKMIG(900
What is your need?
I've been using HIS connected to the z/OS using EE as a transport.
Note, current HIS versions no longer support native SNA.
And usually HIS is not because of connectivity, because every z/OS is
TCP/IP capable. It is because the application rely on SNA.
--
Radoslaw Skorupka
Hi
Visara is around and doing well. Product offerings for storage are VTL and
DASD. The CCA 3074 provides console consolidation and automation.
Email me off line to discuss your needs
Regards
Ken
Kenneth A. Bloom
Avenir Technologies Inc
/d/b/a Visara International
203-984-2235
bl...@visara.c
Visara? I think we had one of those boxes to connect system consoles at
one time. I wasn't the one who connected them up so that's about all I
remember.
On 7/28/2021 12:43 PM, Carmen Vitullo wrote:
I'm thinking Virsa is no longer around :( - or maybe I have the company
name wrong, they had e
I'm thinking Virsa is no longer around :( - or maybe I have the company
name wrong, they had emulators for 3270 controllers we used over EE that
connected from z/os to a windows platform at our agencies using like
controllers and 3270 terminals and printers.
On 7/28/2021 2:32 PM, Carmen Vitull
I think Virsa as a possible solution...It's been a long time but IIRC
they had a viable solution.
Carmen
On 7/28/2021 2:25 PM, Tom Sims wrote:
Greetings,
One of our clients is in the process of retiring their mainframe. They
are looking at Windows Host Integration Server as a possible
repl
Greetings,
One of our clients is in the process of retiring their mainframe. They
are looking at Windows Host Integration Server as a possible replacement
for their Enterprise Extender node, which has been put forward as a
possibility by a remote mainframe partner.
Not a replacement for host
There are some that do I’m sure but I could not name them. A fair amount of
code was ported from z/OS to z/VSE including console support and older version
of CICS/TS. To facilitate that some z/OS simulation is done by the Supervisor
using SVCs and PCs.
Chuck Arney
> On Jul 28, 2021, at 10:46
On Wed, 28 Jul 2021 14:21:14 -0400, David Spiegel wrote:
>
>COPYTREE
>
copytree is a REXX sample
>https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-copytree-make-copy-file-hierarchy-while-preserving-all-file-attributes
>
... which touts many laudable features:
Tolerates errors when setting tar
On 7/28/2021 11:10 AM, Lizette Koehler wrote:
What I do not know is how to copy everything (paths etc. ) from
/tmppath/path/path1 to /newpath1
I usually position to the source directory (using 'cd') and then issue:
pax -rw -peW -XCM . targetdir
--
Phoenix Software International
Edward E. Jaf
The pax command is the way I found to copy from one dir or to another -
part of my maint process is to compare old and new etc filesystems, then
use the pax command to copy new data without overlaying the old data
from omvs change to the dir you are copying from
issue the pax command
pax -r
On Wed, 28 Jul 2021 11:10:06 -0700, Lizette Koehler wrote:
>
>What I do not know is how to copy everything (paths etc. ) from
>/tmppath/path/path1 to /newpath1
>
pax?:
( cd /tmppath/path/path1 && pax -w . ) | ( cd /newpath1 && pax
-rv )
Options for pax could collapse this to a single comm
Hi Lizette,
COPYTREE
https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-copytree-make-copy-file-hierarchy-while-preserving-all-file-attributes
Regards,
David
On 2021-07-28 14:10, Lizette Koehler wrote:
Dearest List -
I am not well trained in USS, partially because I do not need to do it oft
Dearest List -
I am not well trained in USS, partially because I do not need to do it often
I have been asked to do the following. I am not sure of the specific
command in USS or best way to do it. Any specific examples will be helpful
I have mounted on /path a single filesystem consi
Is a unit limited to a single line? Choosing any of those separators loses
functionality, unlike using CRLF. Of course, with Unicode there's NEL, but that
ship has already sailed.
The number of nesting levels is limited by the number of separator characters
defined, which is why I wish that ARP
On Wed, 28 Jul 2021 15:44:16 +, Seymour J Metz wrote:
>
>The Multics developers chose not to use CR because that would have prevented
>overprinting.
>
>If you use RS to separate lines then you can't use it to separate groups of
>lines. There's no equivalent to
>
> foo bar baz Tom Dick H
So z/VSE Supervisor and Data Management macros never expand to a PC?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Chuck [ch...@arneycomputer.com]
Sent: Tuesday, July
Agree with what? I consider CRLF to be the best choice, given the limitations
of ASCII, with RS reasonable if you don't want to support multi-line records.
The Multics developers chose not to use CR because that would have prevented
overprinting.
If you use RS to separate lines then you can't u
On Wed, 28 Jul 2021 14:02:14 +, Seymour J Metz wrote:
>The traditional separator was CRLF, but the Multics developers decide to use a
>single character, and Unix followed suit; I don't know why they didn't choose
>RS ('1E'X) which, IMHO, would have been a much more sensible choice.
>
I heart
The traditional separator was CRLF, but the Multics developers decide to use a
single character, and Unix followed suit; I don't know why they didn't choose
RS ('1E'X) which, IMHO, would have been a much more sensible choice. Maybe the
wanted to support multi-line messages?
--
Shmuel (Seymour
Hello!
I have a stc which has the following jcl in it:
//KLS1 JOB JESLOG=(SPIN,100K),MSGLEVEL=1
..
//TLVLOG DD SYSOUT=&SOUT,SPIN=(UNALLOC,100K)
The SPIN would normally function but currently is not working for this stc.
The files are not being freed.
I have in another lpar the same stc w
On Wed, 28 Jul 2021 12:29:22 +, Seymour J Metz wrote:
>...
>For historical reasons, Unix misused the Line Feed (LF) character as a logical
>new line ...
>
For similar bad historical reasons, z/OS iconv (and UNICODE services generally?)
mistranslates ASCII* LF<->NL EBCDIC, causing compatibi
If you can get the original file with the NL to your mainframe with purely
binary transfers there are a couple of things that can help.
On a zVM CMS system I made a Rexx to do it like this:
/*rexx*/
Parse arg fn ft fm .
Address command
/* splits on 0x15 */
'PIPE <' fn ft fm '| DEBLOCK LINEEND | >'
To start, there is a difference between how certain code points are defined and
how various operating systems use them.
For historical reasons, Unix misused the Line Feed (LF) character as a logical
new line instead of using the more appropriate 2-character CRLF; other systems,
e.g., PC-DOS use
Sometimes it's outright prohibitted, e.g., RFC 8259: "Implementations MUST NOT
add a byte order mark (U+FEFF) to the beginning of a networked-transmitted
JSON text. In the interests of interoperability, implementations that parse
JSON texts MAY ignore the presence of a byte order mark rat
29 matches
Mail list logo
