Downloading macro libraries: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==How can the macro libraries be downloaded?==                                                                                      
This page provides Help for downloading from the "Macro libraries for Sirius Software Inc." page that is accessed from the Rocket website [https://m204.rocketsoftware.com/ Rocket M204 Customer Care] page.
The macro libraries can be downloaded by clicking on                                                                               
 
the link for the macro library with the <b>right</b> mouse                                                                         
==How can the macro libraries be downloaded?==  
button. This will (on most browsers) bring up a pop-up menu                                                                         
The macro libraries can be downloaded by right-clicking the link for the macro library and selecting the save option (<i>Save Link As</i>, <i>Save target As</i>,  
that will have an option <i>Save Link As</i>, <i>Save target As</i>,                                                                
<i>Save As</i> or something similar). Then set the appropriate target directory (and name if desired)  
<i>Save As</i> or something similar. Select this option and then                                                                   
for the file. The macro library will then be downloaded to to  
set the appropriate target directory (and name if desired)                                                                          
the indicated location.  
for the file. The macro library will then be downloaded to to                                                                      
 
the indicated location.                                                                                                            
Alternatively, you can click the <i>left</i> mouse button on  
                                                                                                                                   
the link for a macro library. This will result in the browser  
Alternatively, the <b>left</b> mouse button can be clicked on                                                                      
prompting for whether the file should be saved, where it  
the link for an macro library. This will result in the browser                                                                      
should be saved, and under what name. Some browsers prompt  
prompting the user whether the file should be saved, where it                                                                      
for this information before the macro library is actually  
should be saved and under what name. Some browsers prompt                                                                          
downloaded, others prompt for it after. Obviously, those  
for this information before the macro library is actually                                                                          
that prompt after will present a considerable delay before  
downloaded, others prompt for it after. Obviously, those                                                                            
the prompt. Opera actually prompts as soon as it receives the  
that prompt after will present a considerable delay before                                                                          
file header but continues downloading while waiting for the user response.  
the prompt. Opera actually prompts as soon as it receives the                                                                      
 
file header but continues downloading while waiting for the                                                                        
If the e-mail transfer is selected, the macro library is e-mailed and should
user response.                                                                                                                      
be saved to a local file, then uploaded to the mainframe exactly as  
                                                                                                                                   
if it had been downloaded directly. Receiving the object deck via e-mail  
If the e-mail transfer is selected the macro library will be e-mailed                                                              
allows the library to be sent to a different person/workstation  
to the indicated e-mail address as an attachment. The attachment should                                                            
than the one initiating the request.
be saved to a local file and then uploaded to the mainframe exactly as                                                              
 
if it had been downloaded directly. Receiving the object deck via e-mail                                                            
==How can the macro libraries be uploaded to the mainframe?==  
allows the library to be sent to a different person/workstation                                                                    
Once the macro libraries are downloaded to the workstation, they must  
than the one initiating the request.                                                                                                
be uploaded to the MVS, VM, or VSE system on the IBM mainframe.    
                                                                                                                                   
Any file transfer mechanism can be used including FTP and IND$FILE
==How can the macro libraries be uploaded to the mainframe?==                                                                      
but regardless of the transfer mechanism, some rules must be  
Once the macro libraries are downloaded to the workstation they must                                                                
observed.
be uploaded to the MVS, VM or VSE system on the IBM mainframe.                                                                      
 
Any file transfer mechanism can be used including FTP and IND$FILE                                                                  
First, the macro libraries contain binary data and hence <b>must</b>  
but regardless of the transfer mechanism some rules must be                                                                        
be transferred as binary.  
observed.                                                                                                                          
 
                                                                                                                                   
Second, the format and LRECL of the file must be specified during  
First, the macro libraries contain binary data and hence <b>must</b>                                                                
the upload. This is because most workstation systems (including  
be transferred as binary.                                                                                                          
Windows, Mac OS and Unix) do not have a concept of file formats  
                                                                                                                                   
and LRECL's. This information would be lost if it were not specified  
Second, the format and LRECL of the file must be specified during                                                                  
during the upload. The format of the uploaded file must be <i>F</i> under  
the upload. This is because most workstation systems (including                                                                    
VM systems and <i>FB</i> under MVS and VSE systems. The LRECL must be  
Windows, Mac OS and Unix) do not have a concept of file formats                                                                    
80 on all systems and under MVS and VSE the blocksize can be any multiple  
and LRECL's. This information would be lost if it were not specified                                                                
of 80 though 3120 is a common blocksize for object libraries.  
during the upload. The format of the uploaded file must be <i>F</i> under                                                          
 
VM systems and <i>FB</i> under MVS and VSE systems. The LRECL must be                                                              
When using FTP, the characteristics (RECFM, LRECL and BLOCKSIZE) of  
80 on all systems and under MVS and VSE the blocksize can be any multiple                                                          
the uploaded file can be set with the <i>SITE</i> and <i>LOCSITE</i>  
of 80 though 3120 is a common blocksize for object libraries.                                                                      
FTP commands. The SITE command should be used if the FTP client  
                                                                                                                                   
is on the workstation and the server is on the mainframe. In this case  
When using FTP, the characteristics (RECFM, LRECL and BLOCKSIZE) of                                                                
the SITE command might have to be sent as a "quote" to the mainframe.  
the uploaded file can be set with the <i>SITE</i> and <i>LOCSITE</i>                                                                
How this is done, depends on your workstation's FTP client.
FTP commands. The SITE command should be used if the FTP client                                                                    
The LOCSITE command should be used if the FTP client is on the  
is on the workstation and the server is on the mainframe. In this case                                                              
mainframe and the server is on the workstation.
the SITE command might have to be sent as a "quote" to the mainframe.                                                              
 
How this is done, depends on your workstation's FTP client.                                                                        
Under MVS, you can upload an macro library either as a member of a Partitioned
The LOCSITE command should be used if the FTP client is on the                                                                      
Data Set (PDS) or as an individual sequential file.  A PDS is recommended as  
mainframe and the server is on the workstation.                                                                                    
a good way to collect all your Sirius macro library uploads in one DSN, using  
                                                                                                                                   
the member name to show the product and version.
Under MVS, you can upload an macro library either as a member of a Partitioned                                                      
 
Data Set (PDS) or as an individual sequential file.  A PDS is recommended as                                                        
==What are the Sirius Mods?==  
a good way to collect all your Sirius macro library uploads in one DSN, using                                                      
The <var class="product">Sirius&nbsp;Mods</var> is a collection of functions and enhancements
the member name to show the product and version.                                                                                    
to the core <var class="product">Model&nbsp;204</var> load module. These enhancements are either  
                                                                                                                                   
products in and of themselves, or they are prerequisites for products which  
==What are the Sirius Mods?==                                                                                                      
are written in User Language. A site is authorized to download all of the  
The <i>Sirius&nbsp;Mods</i> is a collection of functions and enhancements                                                          
<var class="product">Sirus&nbsp;Mods</var> if it is licensed for any of the products that  
to the core <i>Model&nbsp;204</i> load module. These enhancements are either                                                        
require these enhancements. Your authorization zap will then enable the  
products in and of themselves, or they are prerequisites for products which                                                        
appropriate set of products.  
are written in User Language. A site is authorized to download all of the                                                          
 
<i>Sirus&nbsp;Mods</i> if it is licensed for any of the products that                                                              
Products that require the <var class="product">Sirius&nbsp;Mods</var> include:  
require these enhancements. Your authorization zap will then enable the                                                            
* Fast/Backup  
appropriate set of products.                                                                                                        
* Fast/Reload                        
                                                                                                                                   
* Fast/Unload User Language Interface    
Products that require the <i>Sirius&nbsp;Mods</i> include:                                                                          
* Janus Network Security  
                                                                                                                                   
* Janus Open Server  
* Fast/Backup                                                                                                                      
* Janus Open Client
* Fast/Reload                                                                                                                      
* Janus SOAP
* Fast/Unload User Language Interface                                                                                              
* Janus Specialty Data Store  
* Janus Network Security                                                                                                            
* Janus TCP/IP Base
* Janus Open Server                                                                                                                
* Janus Web Server  
* Janus Open Client                                                                                                                
* Japanese Functions  
* Janus SOAP                                                                                                                        
* SirDBA          
* Janus Specialty Data Store                                                                                                        
* SirFact                            
* Janus TCP/IP Base                                                                                                                
* SirFile                            
* Janus Web Server                                                                                                                  
* Sirius Performance Enhancements        
* Japanese Functions                                                                                                                
* Sirius Performance Enhancements V2  
* SirDBA                                                                                                                            
* SirLib  
* SirFact                                                                                                                          
* SirMon  
* SirFile                                                                                                                          
* SirPro  
* Sirius Performance Enhancements                                                                                                  
* SirSafe  
* Sirius Performance Enhancements V2                                                                                                
* SirScan
* SirLib                                                                                                                            
* SirTune
* SirMon                                                                                                                            
* SirXref  
* SirPro                                                                                                                            
* Sir2000 Field Migration Facility  
* SirSafe                                                                                                                          
* Sir2000 User Language Tools  
* SirScan                                                                                                                          
* Trusted Login Facility  
* SirTune                                                                                                                          
           
* SirXref                                                                                                                          
You can determine which of these products your site is authorized for by  
* Sir2000 Field Migration Facility                                                                                                  
examining [https://m204.rocketsoftware.com/maint/dlist your customer profile].
* Sir2000 User Language Tools                                                                                                      
After the <var class="product">Sirius&nbsp;Mods</var> are installed you can verify product authorizations by issuing  
* Trusted Login Facility                                                                                                            
the <var>[[ROCKET or SIRIUS command|SIRIUS]]</var> command in an Online running a load module that includes the <var class="product">Sirius&nbsp;Mods</var>.
                                                                                                                                   
 
You can determine which of these products your site is authorized for by                                                            
==Where can more documentation be found?==
examining <a href="https://m204.rocketsoftware.com/dlist">your customer profile</a>.                                                
The Rocket M204 macro libraries are distributed on an as-is basis, so no more
After the <i>Sirius&nbsp;Mods</i> are installed you can verify product authorizations by issuing                                    
documentation is available.  
the <b>SIRIUS</b> command in an Online running a load module that                                                                  
           
includes the <i>Sirius&nbsp;Mods</i>.                                                                                              
==Is there any other help available?==                  
                                                                                                                                   
As always, if you have <i>any</i> questions about the installation of Rocket M204  
==Where can more documentation be found?==                                                                                          
products, you should not hesitate to call our technical  
The Rocket M204 macro libraries are distributed on an as-is basis, so no more                                                      
support number at +1.800.755.4222. You can also e-mail us at  
documentation is available.                                                                                                        
[mailto:m204support@rocketsoftware.com m204support@rocketsoftware.com].
                                                                                                                                   
 
==Is there any other help available?==                                                                                              
As always, if you have <b>any</b> questions about the installation of Rocket M204                                                  
products, you should not hesitate to call our technical                                                                            
support number at +1.800.755.4222. You can also e-mail us at                                                                        
[[mailto:m204support@rocketsoftware.com m204support@rocketsoftware.com]].
[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 21:37, 27 January 2017

This page provides Help for downloading from the "Macro libraries for Sirius Software Inc." page that is accessed from the Rocket website Rocket M204 Customer Care page.

How can the macro libraries be downloaded?

The macro libraries can be downloaded by right-clicking the link for the macro library and selecting the save option (Save Link As, Save target As, Save As or something similar). Then set the appropriate target directory (and name if desired) for the file. The macro library will then be downloaded to to the indicated location.

Alternatively, you can click the left mouse button on the link for a macro library. This will result in the browser prompting for whether the file should be saved, where it should be saved, and under what name. Some browsers prompt for this information before the macro library is actually downloaded, others prompt for it after. Obviously, those that prompt after will present a considerable delay before the prompt. Opera actually prompts as soon as it receives the file header but continues downloading while waiting for the user response.

If the e-mail transfer is selected, the macro library is e-mailed and should be saved to a local file, then uploaded to the mainframe exactly as if it had been downloaded directly. Receiving the object deck via e-mail allows the library to be sent to a different person/workstation than the one initiating the request.

How can the macro libraries be uploaded to the mainframe?

Once the macro libraries are downloaded to the workstation, they must be uploaded to the MVS, VM, or VSE system on the IBM mainframe. Any file transfer mechanism can be used including FTP and IND$FILE, but regardless of the transfer mechanism, some rules must be observed.

First, the macro libraries contain binary data and hence must be transferred as binary.

Second, the format and LRECL of the file must be specified during the upload. This is because most workstation systems (including Windows, Mac OS and Unix) do not have a concept of file formats and LRECL's. This information would be lost if it were not specified during the upload. The format of the uploaded file must be F under VM systems and FB under MVS and VSE systems. The LRECL must be 80 on all systems and under MVS and VSE the blocksize can be any multiple of 80 though 3120 is a common blocksize for object libraries.

When using FTP, the characteristics (RECFM, LRECL and BLOCKSIZE) of the uploaded file can be set with the SITE and LOCSITE FTP commands. The SITE command should be used if the FTP client is on the workstation and the server is on the mainframe. In this case the SITE command might have to be sent as a "quote" to the mainframe. How this is done, depends on your workstation's FTP client. The LOCSITE command should be used if the FTP client is on the mainframe and the server is on the workstation.

Under MVS, you can upload an macro library either as a member of a Partitioned Data Set (PDS) or as an individual sequential file. A PDS is recommended as a good way to collect all your Sirius macro library uploads in one DSN, using the member name to show the product and version.

What are the Sirius Mods?

The Sirius Mods is a collection of functions and enhancements to the core Model 204 load module. These enhancements are either products in and of themselves, or they are prerequisites for products which are written in User Language. A site is authorized to download all of the Sirus Mods if it is licensed for any of the products that require these enhancements. Your authorization zap will then enable the appropriate set of products.

Products that require the Sirius Mods include:

  • Fast/Backup
  • Fast/Reload
  • Fast/Unload User Language Interface
  • Janus Network Security
  • Janus Open Server
  • Janus Open Client
  • Janus SOAP
  • Janus Specialty Data Store
  • Janus TCP/IP Base
  • Janus Web Server
  • Japanese Functions
  • SirDBA
  • SirFact
  • SirFile
  • Sirius Performance Enhancements
  • Sirius Performance Enhancements V2
  • SirLib
  • SirMon
  • SirPro
  • SirSafe
  • SirScan
  • SirTune
  • SirXref
  • Sir2000 Field Migration Facility
  • Sir2000 User Language Tools
  • Trusted Login Facility

You can determine which of these products your site is authorized for by examining your customer profile. After the Sirius Mods are installed you can verify product authorizations by issuing the SIRIUS command in an Online running a load module that includes the Sirius Mods.

Where can more documentation be found?

The Rocket M204 macro libraries are distributed on an as-is basis, so no more documentation is available.

Is there any other help available?

As always, if you have any questions about the installation of Rocket M204 products, you should not hesitate to call our technical support number at +1.800.755.4222. You can also e-mail us at m204support@rocketsoftware.com.