dilluns, 19 d’octubre de 2009

IBM Systems Magazine gratuït

Llegint informació sobre la darrera RPG & DB2 Summit, on ha participat el nostre estimat Scott Klement, he vist un anunci de subscripció gratuïta a la revista IBM Systems Magazine, amb una suculenta URL:

http://www.ibmsystemsmagpowersystemsibmidigital.com

I registrant-se, podem accedir als continguts d'aquest interessant magazine:

dimecres, 7 d’octubre de 2009

DNS resource records

A DNS zone database is made up of a collection of resource records. Each resource record specifies information about a particular object. For example, address mapping (A) records map a host name to an IP address, and reverse-lookup pointer (PTR) records map an IP address to a host name. The server uses these records to answer queries for hosts in its zone. For more information, use the table to view DNS resource records.

Resource record Abbreviation Description
Address Mapping records A The A record specifies the IP address of this host. A records are used to resolve a query for the IP address of a specific domain name. This record type is defined in RFC 1035.
Andrew File System Database records AFSDB The AFSDB record specifies the AFS or DCE address of the object. AFSDB records are used like A records to map a domain name to its AFSDB address; or to map from the domain name of a cell to authenticated name servers for that cell. This record type is defined in RFC 1183.
Canonical Name records CNAME The CNAME record specifies the actual domain name of this object. When DNS queries an aliased name and finds a CNAME record pointing to the canonical name, it then queries that canonical domain name. This record type is defined in RFC 1035.
Host Information records HINFO The HINFO record specifies general information about a host machine. Standard CPU and operating system names are defined in the Assigned Numbers RFC 1700. However, use of the standard numbers is not required. This record type is defined in RFC 1035.
Integrated Services Digital Network records ISDN The ISDN record specifies the address of this object. This record maps a host name to the ISDN address. They are used only in ISDN networks. This record type is defined in RFC 1183.
IP Version 6 Address records AAAA The AAAA record specifies the 128-bit address of a host. AAAA records are used like A records to map a host name to its IP address. Use AAAA records to support IP version 6 addresses, which do not fit the standard A record format. This record type is defined in RFC 1886.
Location records LOC The LOC record specifies the physical location of network components. These records could be used by applications to evaluate network efficiency or map the physical network. This record type is defined in RFC 1876.
Mail Exchanger records MX The MX records defines a mail exchanger host for mail sent to this domain. These records are used by SMTP (Simple Mail Transfer Protocol) to locate hosts that will process or forward mail for this domain, along with preference values for each mail exchanger host. Each mail exchanger host must have a corresponding host address (A) records in a valid zone. This record type is defined in RFC 1035.
Mail Group records MG The MG records specifies the mail group domain name. This record type is defined in RFC 1035.
Mailbox records MB The MB records specifies the host domain name which contains the mailbox for this object. Mail sent to the domain will be directed to the host specified in the MB record. This record type is defined in RFC 1035.
Mailbox Information records MINFO The MINFO records specifies the mailbox that should receive messages or errors for this object. The MINFO record is more commonly used for mailing lists than for a single mailbox. This record type is defined in RFC 1035.
Mailbox Rename records MR The MR records specifies a new domain name for a mailbox. Use the MR record as a forwarding entry for a user who has moved to a different mailbox. This record type is defined in RFC 1035.
Name Server records NS The NS record specifies an authoritative name server for this host. This record type is defined in RFC 1035.
Network Service Access Protocol records NSAP The NSAP record specifies the address of a NSAP resource. NSAP records are used to map domain names to NSAP addresses. This record type is defined in RFC 1706.
Public Key records KEY The KEY record specifies a public key that is associated with a DNS name. The key could be for a zone, a user, or a host. This record type is defined in RFC 2065.
Responsible Person records RP The RP record specifies the internet mail address and description of the person responsible for this zone or host. This record type is defined in RFC 1183.
Reverse-lookup Pointer records PTR The PTR record specifies the domain name of a host for which you want a PTR record defined. PTR records allow a host name lookup, given an IP address. This record type is defined in RFC 1035.
Route Through records RT The RT record specifies a host domain name that can act as a forwarder of IP packets for this host. This record type is defined in RFC 1183.
Start of Authority records SOA The SOA record specifies that this server is authoritative for this zone. An authoritative server is the best source for data within a zone. The SOA record contains general information about the zone and reload rules for secondary servers. There can be only one SOA record per zone. This record type is defined in RFC 1035.
Text records TXT The TXT record specifies multiple strings of text, up to 255 characters long each, to be associated with a domain name. TXT records may be used along with responsible person (RP) records to provide information about who is responsible for a zone. This record type is defined in RFC 1035.
TXT records are used by iSeries DHCP for dynamic updates. The DHCP server writes an associated TXT record for each PTR and A record update done by the DHCP server. DHCP records will have a prefix of AS400DHCP:.
Well-Known Services records WKS The WKS record specifies the well-known services supported by the object. Most commonly, WKS records indicate whether tcp or udp or both protocols are supported for this address. This record type is defined in RFC 1035.
X.400 Address Mapping records PX The PX records is a pointer to X.400/RFC 822 mapping information. This record type is defined in RFC 1664.
X25 Address Mapping records X25 The X25 record specifies the address of an X25 resource. This record maps a host name to the PSDN address. They are used only in X25 networks. This record type is defined in RFC 1183.


Extret del manual d'IBM sobre DNS.

dimarts, 6 d’octubre de 2009

Com pujar un SAVF del PC a l'AS/400

A l'AS/400 crearem l'objecte de tipus SAVF a la biblioteca que ens interesi, en aquest cas CORRETGE1.
CRTSAVF CORRETGE1/ITKSRC
Al PC iniciarem una connexió FTP amb l'AS/400
ftp as400.corretge.ct
Un cop loginejats, indicarem que ens volem moure amb el format de noms complert teclejant
quote site namefmt 1
quote site listfmt 1

Si ho fem desde FileZilla, a l'apartat de log premem botó dret del ratolí Introdueix una ordre específica... i introduim les ordres sense quote.

I ens situarem a la biblioteca on hem creat els SAVF.
cd /qsys.lib/corretge1.lib
Ara ens situarem a la carpeta del PC on tenim els arxius
lcd /home/usuari/arxius
Podem certificar que estem on toca amb la comanda pwd.
Indiquem al servidor FTP que enviarem dades en format binary fent
bin
i pujarem l'arxiu
put itksrc.savf
Un cop pujat, finalitzarem la connexió ftp amb ç
quite

A l'AS/400 visualitzarem informació del SAVF, sobretot esbrinarem com s'ha creat si amb SAVOBJ o amb SAVLIB fent
DSPSAVF CORRETGE1/ITKSRC