Sergio, you don't have VSCS broken into a separate virtual machine. That's OK, we only have it separated because many years ago we had so many CMS users that it was more efficient to run it separate from VTAM.
Try the command: CP REFRESH LOGOVSM VTAM If that works, presuming that you added the comments to the top of your "LOGO CONFIG", change the comment from: /* and: CP REFRESH LOGOVSM VSCS */ to: /* and: CP REFRESH LOGOVSM VTAM */ And... it might not hurt to look up the documentation on the CP REFRESH command, either. :-) Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. -----Original Message----- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Sérgio Lima Costa Sent: Thursday, July 21, 2011 9:28 AM To: IBMVM@LISTSERV.UARK.EDU Subject: RES: RES: Z/VM LOGO don't refresh Hello Mr. Mike. I tried executed what you said here, but still don't work. Look please : Ready; T=0.02/0.03 11:23:35 CP REFRESH LOGOinfo LOGO CONFIG Ready; T=0.01/0.01 11:23:41 CP REFRESH LOGOVSM VSCS HCPZLC6784E VSM VSCS not logged on. Ready(06784); T=0.01/0.01 11:23:56 cp q cpdisk Label Userid Vdev Mode Stat Vol-ID Rdev Type StartLoc EndLoc MNTCF1 MAINT 0CF1 A R/O 540RES 0100 CKD 39 158 MNTCF2 MAINT 0CF2 B R/O 540RES 0100 CKD 159 278 MNTCF3 MAINT 0CF3 C R/O 540RES 0100 CKD 279 398 Ready; T=0.01/0.01 11:24:00 q n PRODPCP -L0073, SYSOUT -L002C, PRODWORK -L0015, PPRC - DSC JOAOCRB - DSC , MARCELO -L006A, SUBJOB - DSC , SERGIOL -L0087 TTRIGO -L002F, SUPCICS -L0022, TECTR01 -L0019, SILVINO -L0044 CLAUDIA -L0054, PERFSVM - DSC , WORKERS1 - DSC , VSESUP - DSC OPERADOR -L005E, PRINTLOG - DSC , VSEPROD1 - DSC , VSEHOMO1 - DSC VTAMOPER - DSC , VTAM - DSC , VMUTIL - DSC , OPERATOR - DSC LOGN0050 - 0050, RSCS - DSC , DEFCICS - DSC , LOGNSYSC - SYSC VSEPROD4 - DSC , CPUVM - DSC , VSEDESV1 - DSC , VSEPROD3 - DSC VSEPROD2 - DSC , DATAMOVE - DSC , DIRMAINT - DSC , VMSERVR - DSC VMSERVS - DSC , GCS - DSC , TCPIP - DSC , OPERSYMP - DSC JARBAS -L001A, FABIO -L0071, CAC4 -L004A, DIONISIO -L0048 ADRIANA -L0004, ROSE -L005C, VANDER -L0056, BEATRIZ -L0050 ANDERS -L0051, SANDRA -L0067, CAC3 -L0040, ENRIQUE -L0081 JALVES -L002E, FELIPE -L0026, MAINT -L0010 VSM - TCPIP VSM - VTAM SUPORTE -H02M87B Any help please ? Thanks, Sergio -----Mensagem original----- De: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] Em nome de Mike Walter Enviada em: quinta-feira, 21 de julho de 2011 11:15 Para: IBMVM@LISTSERV.UARK.EDU Assunto: Re: RES: Z/VM LOGO don't refresh Sergio, If the logo is used by VTAM, you might need an additional command to refresh it. Examine the comments at the top of this partial file(and consider adding them to your LOGO CONFIG, too - I added them to ours as soon as I realized that this is not a task that I perform often, and would not instantly recall the required commands, or their syntax): ---<snip>--- LOGO CONFIG D1 V 80 Trunc=80 Size=69 Line=0 Col=1 Alt=0 ====> |...+....1....+....2....+....3....+....4....+....5....+....6....+....7. ===== * * * Top of File * * * ===== /* Just a reminder that once the SNA logo has been updated, and the */ ===== /* command: CPACCess MAINT CF1 A SR */ ===== /* has been entered, you won't see any update on the logo until after*/ ===== /* command: CP REFRESH LOGOinfo LOGO CONFIG */ ===== /* and: CP REFRESH LOGOVSM VSCS */ ===== /* mrw 03/17/99 */ ===== /*******************************************************************/ ===== /* Logo Configuration File */ ===== /*******************************************************************/ ===== ===== /*----------------------------* ===== * Status Area Definition * ===== *----------------------------*/ ===== ===== Status VM_Read 'VM READ ' , ===== CP_Read 'CP READ ' , ===== Running 'RUNNING ' , ===== More 'MORE... ' , ===== Hold 'HOLDING ' , ===== Not_Accepted 'NOT ACCEPTED' ===== ---<snip>--- Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. -----Original Message----- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Sérgio Lima Costa Sent: Thursday, July 21, 2011 8:14 AM To: IBMVM@LISTSERV.UARK.EDU Subject: RES: RES: Z/VM LOGO don't refresh Hello Malcom, Sorry about my mistake, even though the problem persist. Lookl please : Ready; T=0.01/0.01 10:08:55 CP REFRESH LOGO logo config Ready; T=0.01/0.01 10:09:02 Any Idea? Thanks, Sergio -----Mensagem original----- De: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] Em nome de Malcolm Beattie Enviada em: quinta-feira, 21 de julho de 2011 09:26 Para: IBMVM@LISTSERV.UARK.EDU Assunto: Re: RES: Z/VM LOGO don't refresh Sérgio Lima Costa writes: > When tried use the CP REFRESH command here, We have the error below : [...] > cp refresh logo local logo > > HCPZPM6700E File LOCAL LOGO, record 1: > HCPZPM6701E Invalid logo configuration file statement - ///////////// The file you give to the CP REFRESH command should be the config file which points at the various logo files, not an individual logo file. So you would usually want CP REFRESH LOGO CONFIG It's also worth checking that the logo file that you've changed is actually the one that CP will choose for the logon method you've chosen. For example, LOCAL LOGO will (in the default configuration) only be chosen for local non-SNA 3270 terminals (e.g. OSA-ICC or old-fashioned variants via 2074, 3174, ...) whereas LDEV LOGO will be chosen for logons on logical devices as allocated by, for example, your z/VM TCPIP stack. --Malcolm -- Malcolm Beattie Mainframe Systems and Software Business, Europe IBM UK "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da companhia, o qual é divulgado somente por pessoas autorizadas." "Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect the company's point of view, which is only divulged by authorized personnel." "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da companhia, o qual é divulgado somente por pessoas autorizadas." "Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect the company's point of view, which is only divulged by authorized personnel."