Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: need help on moving files text and data from MCP
137 views
Skip to first unread message
Paul Kimpel
Apr 18, 2018, 2:54:25 PM4/18/18
to
-------- Original Message --------
Subject: Re: need help on moving files text and data from MCP
From: rodger <rodg...@gmail.com>
To:
Date: 4/17/2018 12:13 PM
> On Tuesday, April 17, 2018 at 1:40:08 PM UTC-5, rodger wrote:
>> I have created disk files on pack in MCP world.
>> via cande and program.
>> how do I move the file to windows world, so I can save it to disk.
>> also is it possible to text edit and move it back?
>> I have tried the instructions in Configuring windows to use MCP host name.
>> to no avail.file explorer does not see \\CPMCP1
>> thanks Rodger
>
> also on mapping network drive and log on using CPMCP\administrator
> ADMINISTRATOR is invalid
Getting the SMB/CIFS networking to Windows systems going the first time
can be a challenge. There's a bunch of things that can cause problems,
and it's a difficult thing to diagnose remotely -- trust me, I've done
this a lot. Let me give you some suggestions and see what that may uncover.
1. Since you appear to be able to use the MARC window, I assume that
TCP/IP is up and communicating (i.e., from the Windows side you can ping
192.168.16.5 and get a response. On the ODT you should be able to enter
NW TCPIP PING 192.168.16.6
and get a response from the Windows side as well.
What happens when from the Windows side you try "ping CPMCP1" instead of
using an IP address?
2. Check your MCP host name (ODT HN command). By default that should be
CPMCP1.
3. When you try to map a network drive from the Windows side, do you
actually get the dialog box that asks for your username and password? If
so, that's good -- that means that you are actually connecting to
NX/Services, which is the MCP component that handles SMB/CIFS
networking. It appears you've figured out that the password is
case-sensitive and that the default one is all caps. That is a common
first-time problem.
4. What are you using for a UNC when you attempt to map a drive? At a
minimum you must specify a host name and a share name, i.e.,
\\host\share. If you are just trying to map to "\\CPMCP1", that's going
to give you an error. On Win7, it says "Windows cannot access \\host".
The easiest share name to use when starting out is "_HOME_", which will
connect you to the directory of files you'd normally see if logging on
to CANDE. So you should be using a UNC something like "\\CPMCP1\_HOME_".
Note the two underscores.
5. As an alternative, you can log on to the MCP environment as a whole
from Windows by keying Start > Run... and then entering just the host
portion of a UNC ("\\CPMCP1") in the text box where you'd normally enter
"cmd" to run the command-line shell or "regedit" or some other command.
That should prompt you for your MCP usercode and password, and show you
ALL of the shares on that system you can connect to. If Windows doesn't
open an Explorer window automatically, you can see the shares under the
"Network" node of an Explorer window you open yourself.
Try these and let us know what you get in response. Please try to be
explicit on what you are doing and what responses you get back. Vague
reports of things not working don't give us much to work with in terms
of diagnosis.
Mapping a share from Windows to the MCP environment and using Windows
Explorer is just one way to move files back and forth. That method has a
lot of capability, but it's often not as straightforward as moving files
between two Windows systems, or even between Windows and Unix/Linux.
There are two main issues: EBCDIC/ASCII translation, and the fact that
Windows/*nix use files that are organized as simple streams of bytes
(and for text have LF or CR/LF delimiters between lines) but the MCP by
default uses record-oriented files of specific blocks sizes.
The EBCDIC/ASCII translation will happen automatically for text-oriented
files. The MCP determines text mode based on the FILEKIND and EXTMODE
attributes. Files that do not indicate textual data are transferred
transparently. See the Client Access Services User Guide and Client
Access Services Administration Guide for details (these are in Windows
help file format).
If you just drag a source file from the MCP file system to the Windows
side, you'll get a standard Windows text file with CR/LF line
delimiters. Any sequence number and patchmark columns will be stripped
from the file, but trailing spaces in the text portion of the record
(e.g., for Algol, columns 1-72) will not be trimmed.
If you drag that file from Windows back to the MCP share, it will be
transferred and overwrite the original MCP file, but by default it won't
be in MCP record format -- it will be an EBCDIC byte-stream file with
CR/LF line delimiters. CANDE, the compilers, and most MCP utilities will
refuse to have anything to do with it.
There are a number of things you can do about that:
1. Unisys makes available a plug-in for Windows Explorer that, when you
right-click-drag a file to the MCP side, will pop up a dialog and give
you options on how you want the file to be formatted for the MCP. It can
create a record-oriented file acceptable to CANDE, et al, and will
supply sequence numbers, but they probably won't be the same sequence
numbers you started with.
2. Unisys also makes available a Windows utility program, the MCP File
Copier that will transfer source and text-mode data files (and whole
directories of such files) bidirectionally between a Windows system and
an MCP directory share, converting between stream and record formats. I
use this quite a bit, as it will create Windows files in PWB format,
discussed next.
3. My MCP source editing tool of choice for years has been the venerable
Programmer's Workbench (PWB). This is a GUI editor that understands MCP
source file formats, patch files, and other useful aspects of the MCP
software development ecosystem. It has a service that runs on the MCP
side, usually over TCP/IP port 126. PWB allows you to edit files
directly in the MCP file system. It can also edit files in the Windows
file system, and you can do "Save As" to move files between the two
environments. PWB is a little fussy about the exact format of lines in
one of its Windows files (it must exactly mirror the MCP record layout),
but it has an import tool that will read most Windows text files and
convert them to something it can use. PWB takes a little getting used
to, but it has a good help file that includes some tutorials.
Where do you get these? That brings up the subject of the Installs
share. There is Windows software stored on the MCP side that is
accessible in a shared directory for download and installation on a
Windows system. The UNC is \\host\Installs, e.g., "\\CPMCP1\Installs".
There is a ton of stuff there, and I strongly recommend you only install
what you immediately need. You can always go back and get more later.
You can open up the individual folders and just double-click the .msi
files, but at the root of the share is a program titled "MCPIA.exe"
(IA=Installation Assistant). That gives you a convenient checklist of
what's available, allows you to choose individual items, and it will
install what you select in one go, although you may get a bunch of
security pop-ups you'll need to click through. My recommendations for an
initial set are:
Windows Tools
. ClearPath Integration Software
. . Administration Center (configures Client Access Services)
. . Explorer Extensions for Client Access Services (#1 above)
. . MCP File Copier (#2 above)
. Tools and Utilities
. . Programmers Workbench for ClearPath MCP (#3 above)
DO NOT install Web Enabler (under ClearPath Integration Software) on the
PC where you are hosting MCP Express. Apparently that can mess up your
ODT configuration. It's fine to install this on external systems for use
as a terminal emulator, however.
You can also install the Client Access Services User and Administration
help files from the IA, which might be handy to have on your system for
quick reference.
There are several other ways to move files between Windows/*nix and MCP
environments, including:
* FTP. The MCP FTP implementation can transfer both binary and text
files, and understands how to convert between byte-stream formats on
external systems and the MCP's record formats. You have to tell it to do
that format mapping, however, and the method is a little arcane. See the
TCP/IP Distributed Systems Services (DSS) manual. The FileZilla FTP app
will talk to the MCP FTP service, but you need to tell the MCP to send
its directory listings in Unix format. Once FZ connects to the MCP,
select the Server > Enter custom command... menu item and then enter
"SITE DIR=STANDARD" in the command box. This can be set as the default
using an MCP FTP configuration file.
* The Redirector. This is an MCP API that allows MCP applications to
access files on Windows/Samba shares. It uses a form of file I/O and is
configured through file attributes. It's documented in the I/O Subsystem
Programming Guide under "Using Virtual Files". There is an MCP utility
program, SYSTEM/NXSERVICES/PCDRIVER that uses the Redirector API to
transfer files back and forth between the MCP and a share. This program
is documented in the System Software Utilities manual.
* STREAMIOH. This is a companion to the Redirector that allows an MCP
application to read and write line-delimited byte-stream files as if
they were record-oriented MCP files. It is also configured using file
attributes.
I've written about and made UNITE presentations on these subjects in the
past. You might find some of the following useful:
http://www.digm.com/Resources/Gregory/Using-Stream-Files.pdf
http://www.digm.com/UNITE/2016/index.htm#MCP_4028 (Stream Files)
http://www.digm.com/UNITE/2007/Index.htm (Redirector and STREAMIOH)
http://sourceforge.net/projects/mcppwbcopy/ (an application of Redirector)
--
Paul
Subject: Re: need help on moving files text and data from MCP
From: rodger <rodg...@gmail.com>
To:
Date: 4/17/2018 12:13 PM
> On Tuesday, April 17, 2018 at 1:40:08 PM UTC-5, rodger wrote:
>> I have created disk files on pack in MCP world.
>> via cande and program.
>> how do I move the file to windows world, so I can save it to disk.
>> also is it possible to text edit and move it back?
>> I have tried the instructions in Configuring windows to use MCP host name.
>> to no avail.file explorer does not see \\CPMCP1
>> thanks Rodger
>
> also on mapping network drive and log on using CPMCP\administrator
> ADMINISTRATOR is invalid
Getting the SMB/CIFS networking to Windows systems going the first time
can be a challenge. There's a bunch of things that can cause problems,
and it's a difficult thing to diagnose remotely -- trust me, I've done
this a lot. Let me give you some suggestions and see what that may uncover.
1. Since you appear to be able to use the MARC window, I assume that
TCP/IP is up and communicating (i.e., from the Windows side you can ping
192.168.16.5 and get a response. On the ODT you should be able to enter
NW TCPIP PING 192.168.16.6
and get a response from the Windows side as well.
What happens when from the Windows side you try "ping CPMCP1" instead of
using an IP address?
2. Check your MCP host name (ODT HN command). By default that should be
CPMCP1.
3. When you try to map a network drive from the Windows side, do you
actually get the dialog box that asks for your username and password? If
so, that's good -- that means that you are actually connecting to
NX/Services, which is the MCP component that handles SMB/CIFS
networking. It appears you've figured out that the password is
case-sensitive and that the default one is all caps. That is a common
first-time problem.
4. What are you using for a UNC when you attempt to map a drive? At a
minimum you must specify a host name and a share name, i.e.,
\\host\share. If you are just trying to map to "\\CPMCP1", that's going
to give you an error. On Win7, it says "Windows cannot access \\host".
The easiest share name to use when starting out is "_HOME_", which will
connect you to the directory of files you'd normally see if logging on
to CANDE. So you should be using a UNC something like "\\CPMCP1\_HOME_".
Note the two underscores.
5. As an alternative, you can log on to the MCP environment as a whole
from Windows by keying Start > Run... and then entering just the host
portion of a UNC ("\\CPMCP1") in the text box where you'd normally enter
"cmd" to run the command-line shell or "regedit" or some other command.
That should prompt you for your MCP usercode and password, and show you
ALL of the shares on that system you can connect to. If Windows doesn't
open an Explorer window automatically, you can see the shares under the
"Network" node of an Explorer window you open yourself.
Try these and let us know what you get in response. Please try to be
explicit on what you are doing and what responses you get back. Vague
reports of things not working don't give us much to work with in terms
of diagnosis.
Mapping a share from Windows to the MCP environment and using Windows
Explorer is just one way to move files back and forth. That method has a
lot of capability, but it's often not as straightforward as moving files
between two Windows systems, or even between Windows and Unix/Linux.
There are two main issues: EBCDIC/ASCII translation, and the fact that
Windows/*nix use files that are organized as simple streams of bytes
(and for text have LF or CR/LF delimiters between lines) but the MCP by
default uses record-oriented files of specific blocks sizes.
The EBCDIC/ASCII translation will happen automatically for text-oriented
files. The MCP determines text mode based on the FILEKIND and EXTMODE
attributes. Files that do not indicate textual data are transferred
transparently. See the Client Access Services User Guide and Client
Access Services Administration Guide for details (these are in Windows
help file format).
If you just drag a source file from the MCP file system to the Windows
side, you'll get a standard Windows text file with CR/LF line
delimiters. Any sequence number and patchmark columns will be stripped
from the file, but trailing spaces in the text portion of the record
(e.g., for Algol, columns 1-72) will not be trimmed.
If you drag that file from Windows back to the MCP share, it will be
transferred and overwrite the original MCP file, but by default it won't
be in MCP record format -- it will be an EBCDIC byte-stream file with
CR/LF line delimiters. CANDE, the compilers, and most MCP utilities will
refuse to have anything to do with it.
There are a number of things you can do about that:
1. Unisys makes available a plug-in for Windows Explorer that, when you
right-click-drag a file to the MCP side, will pop up a dialog and give
you options on how you want the file to be formatted for the MCP. It can
create a record-oriented file acceptable to CANDE, et al, and will
supply sequence numbers, but they probably won't be the same sequence
numbers you started with.
2. Unisys also makes available a Windows utility program, the MCP File
Copier that will transfer source and text-mode data files (and whole
directories of such files) bidirectionally between a Windows system and
an MCP directory share, converting between stream and record formats. I
use this quite a bit, as it will create Windows files in PWB format,
discussed next.
3. My MCP source editing tool of choice for years has been the venerable
Programmer's Workbench (PWB). This is a GUI editor that understands MCP
source file formats, patch files, and other useful aspects of the MCP
software development ecosystem. It has a service that runs on the MCP
side, usually over TCP/IP port 126. PWB allows you to edit files
directly in the MCP file system. It can also edit files in the Windows
file system, and you can do "Save As" to move files between the two
environments. PWB is a little fussy about the exact format of lines in
one of its Windows files (it must exactly mirror the MCP record layout),
but it has an import tool that will read most Windows text files and
convert them to something it can use. PWB takes a little getting used
to, but it has a good help file that includes some tutorials.
Where do you get these? That brings up the subject of the Installs
share. There is Windows software stored on the MCP side that is
accessible in a shared directory for download and installation on a
Windows system. The UNC is \\host\Installs, e.g., "\\CPMCP1\Installs".
There is a ton of stuff there, and I strongly recommend you only install
what you immediately need. You can always go back and get more later.
You can open up the individual folders and just double-click the .msi
files, but at the root of the share is a program titled "MCPIA.exe"
(IA=Installation Assistant). That gives you a convenient checklist of
what's available, allows you to choose individual items, and it will
install what you select in one go, although you may get a bunch of
security pop-ups you'll need to click through. My recommendations for an
initial set are:
Windows Tools
. ClearPath Integration Software
. . Administration Center (configures Client Access Services)
. . Explorer Extensions for Client Access Services (#1 above)
. . MCP File Copier (#2 above)
. Tools and Utilities
. . Programmers Workbench for ClearPath MCP (#3 above)
DO NOT install Web Enabler (under ClearPath Integration Software) on the
PC where you are hosting MCP Express. Apparently that can mess up your
ODT configuration. It's fine to install this on external systems for use
as a terminal emulator, however.
You can also install the Client Access Services User and Administration
help files from the IA, which might be handy to have on your system for
quick reference.
There are several other ways to move files between Windows/*nix and MCP
environments, including:
* FTP. The MCP FTP implementation can transfer both binary and text
files, and understands how to convert between byte-stream formats on
external systems and the MCP's record formats. You have to tell it to do
that format mapping, however, and the method is a little arcane. See the
TCP/IP Distributed Systems Services (DSS) manual. The FileZilla FTP app
will talk to the MCP FTP service, but you need to tell the MCP to send
its directory listings in Unix format. Once FZ connects to the MCP,
select the Server > Enter custom command... menu item and then enter
"SITE DIR=STANDARD" in the command box. This can be set as the default
using an MCP FTP configuration file.
* The Redirector. This is an MCP API that allows MCP applications to
access files on Windows/Samba shares. It uses a form of file I/O and is
configured through file attributes. It's documented in the I/O Subsystem
Programming Guide under "Using Virtual Files". There is an MCP utility
program, SYSTEM/NXSERVICES/PCDRIVER that uses the Redirector API to
transfer files back and forth between the MCP and a share. This program
is documented in the System Software Utilities manual.
* STREAMIOH. This is a companion to the Redirector that allows an MCP
application to read and write line-delimited byte-stream files as if
they were record-oriented MCP files. It is also configured using file
attributes.
I've written about and made UNITE presentations on these subjects in the
past. You might find some of the following useful:
http://www.digm.com/Resources/Gregory/Using-Stream-Files.pdf
http://www.digm.com/UNITE/2016/index.htm#MCP_4028 (Stream Files)
http://www.digm.com/UNITE/2007/Index.htm (Redirector and STREAMIOH)
http://sourceforge.net/projects/mcppwbcopy/ (an application of Redirector)
--
Paul
0 new messages