Migrating to Windows
Deskin, Bob
Bob.Deskin@Cognos.COM
Sat, 20 Nov 2004 08:56:57 -0500
This is a multi-part message in MIME format.
------_=_NextPart_001_01C4CF08.CCEA7487
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C4CF08.CCEA7487"
------_=_NextPart_002_01C4CF08.CCEA7487
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I was in contact with the people who make and support MPUX. The =
discussion was along the same lines as those we had with the IMAGE =
Emulator vendors. However, from a PowerHouse perspective, supporting the =
full MPUX capability would require a significant development effort =
because of the internal changes required. I don't mean that the changes =
would be difficult but they would be extensive.
=20
For example, every case where we call an operating system or file system =
routine is currently conditionally compiled based on the platform. This =
is how we do common source. All the generic code is the same across =
platforms. If we have two calls for similar functions, we need to be =
able to distinguish between them. This means locating all the calls and =
adding conditionals. For example, if we supported the KSAM MPUX calls we =
would have to distinguish between KSAM and C-ISAM or KSAM and DISAM =
depending on the platform because those are our indexed calls. We would =
have to add something to the dictionary and then, and this is the big =
job, locate all the calls in our code and add a conditional based on the =
dictionary entry. Other file system and OS calls would be equally an =
issue.
=20
Yes, we added Eloquence (IMAGE Emulator) support, but those calls were =
not a choice because IMAGE did not exist on other platforms. Rather, we =
had to locate the IMAGE calls and simple change the conditional compile =
to be based on Eloquence or IMAGE rather than the platform (MPE/iX). =
This is how we were able to very easily build an AIX version when the =
request came in.
=20
In addition, we were told that the MPUX KSAM supported the COBOL based =
calls while PowerHouse uses the other type of call.
=20
The other option was to attempt to create an MPUX specific version of =
PowerHouse. However, this too would have required a lot of testing and =
ensuring that MPUX was a 100% MPE/iX emulator. Unfortunately we do not =
have the resources for that nor do we see that there is enough business =
to justify the major effort.
=20
All that said, my understanding is that there is a way to have operating =
system commands from within PowerHouse (such as the COMMAND statement) =
recognized by MPUX. I suggest that you contact your MPUX vendor or =
support and ask.
=20
Bob Deskin =20
Senior Product Manager, Application Development Tools=20
Cognos Inc. 3755 Riverside Drive, Ottawa ON K1G 4K9 CANADA=20
bob.deskin@cognos.com (613) 738-1338 ext 7268=20
-----Original Message-----
From: powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of Roger B. Glayzer
Sent: November 19, 2004 7:55 PM
To: powerh-l@lists.sowder.com
Subject: Migrating to Windows
Here is another migration question concerning HP3000 (928 / Rel C.60.00) =
running PowerHouse Rel 8.39.C to a Windows server (XP) running PC =
Powerhouse 8.43D.
=20
We started to investigate MPUX - a service that runs on the Windows =
Server that can emulate the HP in regards to job scheduling,
spooler functionality, SORT and FCOPY utilities. This was primarily due =
to not wanting to rewrite our HP jobs to some other scripting language. =
Also it would be nice to train our crew gradually to a new OS by =
carrying over some of the functionality that the HP has in regards to =
'debugging' jobs via stdlists.
=20
Does anyone know how to make MPUX communicate with Powerhouse. We had =
hoped that since MPUX has been around for a few years and with the =
announcement about the 3000 disappearing, that there would be some =
'linkage' between Powerhouse and MPUX. We were hoping that MPUX would be =
able to 'intercept' a command coming out of Powerhouse -- if the =
command was something that MPUX could emulate (ie. STREAM, LISTF, =
SORT.......) then MPUX would do its thing else it would just ignore it =
and leave it for the OS to take care of.
=20
Does Cognos have any plans to 'link' with MPUX somehow to make the =
migration from the HP to a Windows platform a little easier?
=20
Does anyone know how to one could 'link' these two programs so they can =
communicate?
=20
This is not a long term permanent solution but it would ease the pain =
slightly if we do not get hit all at once by having to rewrite all our =
HP scripts. The HP has some great features and it would be nice to keep =
some of its ease of use.=20
=20
Thanks for your response in advance.
=20
Roger=20
=20
This message may contain privileged and/or confidential =
information. If you have received this e-mail in error or are not the =
intended recipient, you may not use, copy, disseminate or distribute it; =
do not open any attachments, delete it immediately from your system and =
notify the sender promptly by e-mail that you have done so. Thank you.=20
=20
------_=_NextPart_002_01C4CF08.CCEA7487
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML xmlns:eXclaimer=3D"http://www.exclaimer.co.uk">
<HEAD>
<META http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-16">
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUTF-16">
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Message</TITLE>
<STYLE>P.msoNormal {
FONT-WEIGHT: normal; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: =
black; FONT-FAMILY: "MS Sans Serif", "sans serif"
}
LI.msoNormal {
FONT-WEIGHT: normal; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: =
black; FONT-FAMILY: "MS Sans Serif", "sans serif"
}
BODY {
FONT-WEIGHT: normal; FONT-SIZE: 12pt; MARGIN-LEFT: 50px; COLOR: black; =
FONT-FAMILY: "MS Sans Serif", "sans serif"
}
HR {
WIDTH: 100%; COLOR: #00ffff; HEIGHT: 1px
}
</STYLE>
<META content=3D"MSHTML 5.50.4943.400" name=3DGENERATOR></HEAD><BODY =
bgColor=3D#ffffff background=3Dcid:299394413@20112004-09c8><DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans Serif"'>I =
was in=20
contact with the people who make and support MPUX. The discussion was =
along the=20
same lines as those we had with the IMAGE Emulator vendors. However, =
from a=20
PowerHouse perspective, supporting the full MPUX capability would =
require a=20
significant development effort because of the internal changes required. =
I don't=20
mean that the changes would be difficult but they would be=20
extensive.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans Serif"'>For =
example,=20
every case where we call an operating system or file system routine =
is=20
currently conditionally compiled based on the platform. This is how we =
do common=20
source. All the generic code is the same across platforms. If we have =
two calls=20
for similar functions, we need to be able to distinguish between them. =
This=20
means locating all the calls and adding conditionals. For example, if we =
supported the KSAM MPUX calls we would have to distinguish between KSAM =
and=20
C-ISAM or KSAM and DISAM depending on the platform because those are our =
indexed=20
calls. We would have to add something to the dictionary and then, and =
this is=20
the big job, locate all the calls in our code and add a conditional =
based on the=20
dictionary entry. Other file system and OS calls would be equally an=20
issue.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans =
Serif"'>Yes, we added=20
Eloquence (IMAGE Emulator) support, but those calls were not a choice =
because=20
IMAGE did not exist on other platforms. Rather, we had to locate the =
IMAGE calls=20
and simple change the conditional compile to be based on Eloquence or =
IMAGE=20
rather than the platform (MPE/iX). This is how we were able to very =
easily build=20
an AIX version when the request came in.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004><FONT=20
face=3D'"MS Sans Serif"'></FONT></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans Serif"'>In =
addition, we=20
were told that the MPUX KSAM supported the COBOL based calls while =
PowerHouse=20
uses the other type of call.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans Serif"'>The =
other=20
option was to attempt to create an MPUX specific version of PowerHouse. =
However,=20
this too would have required a lot of testing and ensuring that MPUX was =
a 100%=20
MPE/iX emulator. Unfortunately we do not have the resources for that nor =
do we=20
see that there is enough business to justify the major=20
effort.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3D'"MS Sans Serif"'>All =
that said,=20
my understanding is that there is a way to have operating system =
commands from=20
within PowerHouse (such as the COMMAND statement) recognized by MPUX. I =
suggest=20
that you contact your MPUX vendor or support and =
ask.</FONT></SPAN></DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D299394413-20112004><FONT face=3DArial size=3D2>Bob=20
Deskin &=
nbsp; =20
</FONT><BR><FONT face=3DArial size=3D2>Senior</FONT> <FONT face=3DArial =
size=3D2>Product=20
Manager</FONT><FONT face=3DArial size=3D2>,</FONT> <FONT face=3DArial=20
size=3D2>Application Development Tools</FONT> <BR><FONT face=3DArial =
size=3D2>Cognos=20
Inc.</FONT><FONT face=3DArial size=3D2></FONT> <FONT face=3DArial =
size=3D2>3755=20
Riverside Drive</FONT><FONT face=3DArial size=3D2>,</FONT> <FONT =
face=3DArial=20
size=3D2>Ottawa ON K1G 4K9 CANADA</FONT> <BR><FONT face=3DArial=20
size=3D2>bob.deskin@cognos.com</FONT><FONT face=3DArial size=3D2></FONT> =
<FONT=20
face=3DArial size=3D2>(613) 738-1338 ext</FONT> <FONT face=3DArial =
size=3D2>7268</FONT>=20
</DIV></SPAN>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com]<B>On=20
Behalf Of </B>Roger B. Glayzer<BR><B>Sent:</B> November 19, 2004 7:55=20
PM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Subject:</B> =
Migrating to=20
Windows<BR><BR></FONT></DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>Here is=20
another migration question concerning HP3000 (928 / Rel C.60.00) =
running=20
PowerHouse Rel 8.39.C to a Windows server (XP) running PC Powerhouse=20
8.43D.</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>We started to=20
investigate MPUX - a service that runs on the Windows Server that can =
emulate=20
the HP in regards to job scheduling,</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004>spooler functionality, SORT and =
FCOPY=20
utilities. This was primarily due to not wanting to rewrite our HP =
jobs=20
to some other scripting language. Also it would be nice to train =
our crew=20
gradually to a new OS by carrying over some of the functionality that =
the HP=20
has in regards to 'debugging' jobs via stdlists.</SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004><FONT=20
face=3D'"MS Sans Serif"'></FONT></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>Does anyone=20
know how to make MPUX communicate with Powerhouse. We had hoped that =
since=20
MPUX has been around for a few years and with the announcement about =
the 3000=20
disappearing, that there would be some 'linkage' between Powerhouse =
and MPUX.=20
We were hoping that MPUX would be able to 'intercept' a =
command=20
coming out of Powerhouse -- if the command was something that =
MPUX could=20
emulate (ie. STREAM, LISTF, SORT.......) then MPUX would do its thing =
else it=20
would just ignore it and leave it for the OS to take care=20
of.</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>Does Cognos=20
have any plans to 'link' with MPUX somehow to make the migration from =
the HP=20
to a Windows platform a little easier?</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>Does anyone=20
know how to one could 'link' these two programs so they can=20
communicate?</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004><FONT=20
face=3D'"MS Sans Serif"'></FONT></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>This is=20
not a long term permanent solution but it would ease the =
pain=20
slightly if we do not get hit all at once by having to rewrite all our =
HP=20
scripts. The HP has some great features and it would be nice to keep =
some of=20
its ease of use. </FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT face=3D'"MS Sans =
Serif"'>Thanks for=20
your response in advance.</FONT></SPAN></DIV>
<DIV><SPAN class=3D243132400-20112004></SPAN> </DIV>
<DIV><SPAN class=3D243132400-20112004><FONT=20
face=3D'"MS Sans Serif"'>Roger</FONT></SPAN></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV>
<DIV>
<P> <FONT FACE=3D"Arial" =
SIZE=3D"2">This message may contain privileged and/or confidential =
information. If you have received this e-mail in error or are not =
the intended recipient, you may not use, copy, disseminate or distribute =
it; do not open any attachments, delete it immediately from your system =
and notify the sender promptly by e-mail that you have done so. =
Thank you.</FONT>
</P>
</DIV></BODY></HTML>
------_=_NextPart_002_01C4CF08.CCEA7487--
------_=_NextPart_001_01C4CF08.CCEA7487
Content-Type: image/jpeg;
name="Notebook.jpg"
Content-Transfer-Encoding: base64
Content-ID: <299394413@20112004-09c8>
Content-Description: Notebook.jpg
Content-Location: Notebook.jpg
/9j/4AAQSkZJRgABAgEASABIAAD/7QSyUGhvdG9zaG9wIDMuMAA4QklNA+kAAAAAAHgAAwAAAEgA
SAAAAAADBgJS//f/9wMPAlsDRwUoA/wAAgAAAEgASAAAAAAC2AIoAAEAAABkAAAAAQADAwMAAAAB
Jw8AAQABAAAAAAAAAAAAAAAAYAgAGQGQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4
QklNA+0AAAAAABAASAAAAAEAAQBIAAAAAQABOEJJTQPzAAAAAAAIAAAAAAAAAAA4QklNBAoAAAAA
AAEAADhCSU0nEAAAAAAACgABAAAAAAAAAAI4QklNA/UAAAAAAEgAL2ZmAAEAbGZmAAYAAAAAAAEA
L2ZmAAEAoZmaAAYAAAAAAAEAMgAAAAEAWgAAAAYAAAAAAAEANQAAAAEALQAAAAYAAAAAAAE4QklN
A/gAAAAAAHAAAP////////////////////////////8D6AAAAAD/////////////////////////
////A+gAAAAA/////////////////////////////wPoAAAAAP//////////////////////////
//8D6AAAOEJJTQQAAAAAAAACAAA4QklNBAIAAAAAAAIAADhCSU0ECAAAAAAAEAAAAAEAAAJAAAAC
QAAAAAA4QklNBAkAAAAAAqIAAAABAAAAgAAAAAIAAAGAAAADAAAAAoYAGAAB/9j/4AAQSkZJRgAB
AgEASABIAAD//gAnRmlsZSB3cml0dGVuIGJ5IEFkb2JlIFBob3Rvc2hvcKggNC4wAP/uAA5BZG9i
ZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwMDAwMEQwMDAwMDAwM
DAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwMDAwMEREMDAwMDAwR
DAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIAAIAgAMBIgACEQEDEQH/3QAEAAj/xAE/
AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkK
CxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWS
U/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpam
tsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGx
QiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSV
xNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/APROif0Kv6X81T9L
j+ar/m/5K0F8rJJIfqlJfKySKn6pSXyskkp+qUl8rJJKfqlJfKySSn6pSXyskkp+qUl8rJJKfqlJ
fKySSn//2ThCSU0EBgAAAAAABwABAAAAAQEA//4AJ0ZpbGUgd3JpdHRlbiBieSBBZG9iZSBQaG90
b3Nob3CoIDQuMAD/7gAOQWRvYmUAZIAAAAAB/9sAhAAMCAgNCQ0VDAwVGhQQFBogGxoaGyAiFxcX
FxciEQwMDAwMDBEMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMAQ0NDREOERsRERsUDg4OFBQO
Dg4OFBEMDAwMDBERDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAz/wAARCAAYBaAD
ASIAAhEBAxEB/90ABABa/8QBPwAAAQUBAQEBAQEAAAAAAAAAAwABAgQFBgcICQoLAQABBQEBAQEB
AQAAAAAAAAABAAIDBAUGBwgJCgsQAAEEAQMCBAIFBwYIBQMMMwEAAhEDBCESMQVBUWETInGBMgYU
kaGxQiMkFVLBYjM0coLRQwclklPw4fFjczUWorKDJkSTVGRFwqN0NhfSVeJl8rOEw9N14/NGJ5Sk
hbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2N0dXZ3eHl6e3x9fn9xEAAgIBAgQEAwQFBgcHBgU1AQAC
EQMhMRIEQVFhcSITBTKBkRShsUIjwVLR8DMkYuFygpJDUxVjczTxJQYWorKDByY1wtJEk1SjF2RF
VTZ0ZeLys4TD03Xj80aUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9ic3R1dnd4eXp7fH/9oADAMB
AAIRAxEAPwCv0T+n4/8AxrP+qavW15J0U/r+P/xrP+qavWg8eKElsWSHZfXWYe4A+ZUMjIFTJBE/
Fc1kXbg63mJP+amk0uesGqdc19Sup2ZrLmWGQxwLR4B35v8A0V0qKlJJJIqUkkkkpSSSSSlJJJJK
UkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSS
SSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJ
KUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpS
SSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJ
JKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkp
SSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJ
JJKUkkkkpSSSSSn/0J9G6oKn04zKKXOdYA6x7d1kOP8Ag/3Hs/MXY/sOl/0hYfCT/wCQavnZJArQ
/S1HTXVN21+weYa7/vqzcroeQ+Q3XcYOn/mbF89pIaJfpboXRK+k1uDQPUsILyONPotZ/JatRfKq
SSX6qSXyqkip+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJ
KfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp
+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6
qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqp
JfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl
8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXy
qkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKq
SSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJ
KfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp
+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6
qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn/2Q==
------_=_NextPart_001_01C4CF08.CCEA7487--